[Bug fortran/30887] %VAL only accepts default-kind integer/real/complex

2007-02-28 Thread burnus at gcc dot gnu dot org
--- Comment #8 from burnus at gcc dot gnu dot org 2007-02-28 18:17 --- Subject: Bug 30887 Author: burnus Date: Wed Feb 28 18:17:34 2007 New Revision: 122409 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=122409 Log: 2007-02-28 Tobias Burnus [EMAIL PROTECTED] Paul

[Bug fortran/30887] %VAL only accepts default-kind integer/real/complex

2007-02-28 Thread burnus at gcc dot gnu dot org
--- Comment #9 from burnus at gcc dot gnu dot org 2007-02-28 18:26 --- Fixed in GCC 4.3, not part of 4.2 = close PR. Thanks for having reported this bug. -- burnus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/30887] %VAL only accepts default-kind integer/real/complex

2007-02-23 Thread p dot w dot draper at durham dot ac dot uk
--- Comment #7 from p dot w dot draper at durham dot ac dot uk 2007-02-23 15:44 --- Tried out the patch and it works for me under 64bit with default sized integers. Seems to have fixed PR 30888 too. Thanks. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30887

[Bug fortran/30887] %VAL only accepts default-kind integer/real/complex

2007-02-22 Thread sdirkse at gams dot com
--- Comment #3 from sdirkse at gams dot com 2007-02-22 18:52 --- I took out the restriction in resolve.c that leads to the error message, and it does give me a clean compile, but the code does not do what I expect. For example, passing a real(kind=8) by-value to C doesn't get me a good

[Bug fortran/30887] %VAL only accepts default-kind integer/real/complex

2007-02-22 Thread kargl at gcc dot gnu dot org
--- Comment #4 from kargl at gcc dot gnu dot org 2007-02-22 19:24 --- (In reply to comment #3) Enough facts, now for some ignorant speculation: I suppose there is some logic missing to pass a value from the caller when the size of the value is not the default size (i.e. 4 for my

[Bug fortran/30887] %VAL only accepts default-kind integer/real/complex

2007-02-22 Thread burnus at gcc dot gnu dot org
-- burnus at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |burnus at gcc dot gnu dot |dot org

[Bug fortran/30887] %VAL only accepts default-kind integer/real/complex

2007-02-22 Thread patchapp at dberlin dot org
--- Comment #5 from patchapp at dberlin dot org 2007-02-22 21:10 --- Subject: Bug number PR30887 A patch for this bug has been added to the patch tracker. The mailing list url for the patch is http://gcc.gnu.org/ml/gcc-patches/2007-02/msg01839.html --

[Bug fortran/30887] %VAL only accepts default-kind integer/real/complex

2007-02-22 Thread sdirkse at gams dot com
--- Comment #6 from sdirkse at gams dot com 2007-02-22 21:35 --- (In reply to comment #4) (In reply to comment #3) Enough facts, now for some ignorant speculation: I suppose there is some logic missing to pass a value from the caller when the size of the value is not the

[Bug fortran/30887] %VAL only accepts default-kind integer/real/complex

2007-02-20 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2007-02-20 17:32 --- Paul, do you remember why you have added the following restriction? (The example is accepted by ifort, nagf95 and g95.) resolve.c: if (((e-ts.type == BT_REAL || e-ts.type == BT_COMPLEX)

[Bug fortran/30887] %VAL only accepts default-kind integer/real/complex

2007-02-20 Thread paulthomas2 at wanadoo dot fr
--- Comment #2 from paulthomas2 at wanadoo dot fr 2007-02-21 05:16 --- Subject: Re: %VAL only accepts default-kind integer/real/complex Tobias, --- Comment #1 from burnus at gcc dot gnu dot org 2007-02-20 17:32 --- Paul, do you remember why you have added the following