[Bug fortran/18565] gfortran: CONJG: false error message about standard violation

2005-01-29 Thread cvs-commit at gcc dot gnu dot org
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-01-29 17:46 --- Subject: Bug 18565 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-01-29 17:46:35 Modified files: gcc/fortran: ChangeLog check.c intrinsic.c

[Bug fortran/18565] gfortran: CONJG: false error message about standard violation

2005-01-29 Thread pbrook at gcc dot gnu dot org
--- Additional Comments From pbrook at gcc dot gnu dot org 2005-01-29 17:48 --- Fixed. -- What|Removed |Added Status|NEW |RESOLVED

[Bug fortran/18565] gfortran: CONJG: false error message about standard violation

2005-01-27 Thread sgk at troutmask dot apl dot washington dot edu
--- Additional Comments From sgk at troutmask dot apl dot washington dot edu 2005-01-27 21:55 --- New patch at http://gcc.gnu.org/ml/gcc-patches/2005-01/msg02076.html. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18565

[Bug fortran/18565] gfortran: CONJG: false error message about standard violation

2005-01-26 Thread coudert at clipper dot ens dot fr
--- Additional Comments From coudert at clipper dot ens dot fr 2005-01-26 09:08 --- The same bug happens with aimag (and, as far as I can see, for the same reasons): $ cat a.f90 program bug implicit none complex(8) x write(*,*) aimag(x) end $ gfortran -std=f95 a.f90 In

[Bug fortran/18565] gfortran: CONJG: false error message about standard violation

2005-01-26 Thread coudert at clipper dot ens dot fr
--- Additional Comments From coudert at clipper dot ens dot fr 2005-01-26 19:23 --- Compiling with -std=f95, you can also get these errors: Error: Type of argument 'x' in call to 'cos' at (1) should be REAL(4), not COMPLEX(8) Error: Type of argument 'x' in call to 'exp' at (1) should

[Bug fortran/18565] gfortran: CONJG: false error message about standard violation

2005-01-26 Thread sgk at troutmask dot apl dot washington dot edu
--- Additional Comments From sgk at troutmask dot apl dot washington dot edu 2005-01-27 03:23 --- FX, The first of errors with COS() and friends is caused by marking DCOS as GFC_STD_F77, which apparent is not a subset of GFC_STD_F95. You did not show the code that gives the second set

[Bug fortran/18565] gfortran: CONJG: false error message about standard violation

2005-01-23 Thread sgk at troutmask dot apl dot washington dot edu
--- Additional Comments From sgk at troutmask dot apl dot washington dot edu 2005-01-23 18:16 --- See http://gcc.gnu.org/ml/fortran/2005-01/msg00284.html for a patch. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18565

[Bug fortran/18565] gfortran: CONJG: false error message about standard violation

2004-11-23 Thread toon at moene dot indiv dot nluug dot nl
--- Additional Comments From toon at moene dot indiv dot nluug dot nl 2004-11-24 00:26 --- Subject: Re: gfortran: CONJG: false error message about standard violation sgk at troutmask dot apl dot washington dot edu wrote: --- Additional Comments From sgk at troutmask dot apl dot

[Bug fortran/18565] gfortran: CONJG: false error message about standard violation

2004-11-23 Thread toon at moene dot indiv dot nluug dot nl
--- Additional Comments From toon at moene dot indiv dot nluug dot nl 2004-11-24 00:33 --- Subject: Re: gfortran: CONJG: false error message about standard violation sgk at troutmask dot apl dot washington dot edu wrote: --- Additional Comments From sgk at troutmask dot apl dot

[Bug fortran/18565] gfortran: CONJG: false error message about standard violation

2004-11-21 Thread sgk at troutmask dot apl dot washington dot edu
--- Additional Comments From sgk at troutmask dot apl dot washington dot edu 2004-11-22 01:43 --- Toon, Don't you have commit access to the tree? You can fix this under the obvious rule. -- steve -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18565

[Bug fortran/18565] gfortran: CONJG: false error message about standard violation

2004-11-21 Thread sgk at troutmask dot apl dot washington dot edu
--- Additional Comments From sgk at troutmask dot apl dot washington dot edu 2004-11-22 04:19 --- Toon, I take it back. The code as written is correct. DCONJG is not listed in 13.6 Specific names for standard intrinsic functions of the current standard. It you change the code, then

[Bug fortran/18565] gfortran: CONJG: false error message about standard violation

2004-11-20 Thread toon at moene dot indiv dot nluug dot nl
--- Additional Comments From toon at moene dot indiv dot nluug dot nl 2004-11-20 12:03 --- (In reply to comment #0) z2 = conjg (z1) 1 Error: Type of argument 'z' in call to 'conjg' at (1) should be COMPLEX(4), not COMPLEX(8) Yep, I think this in intrinsic.c:

[Bug fortran/18565] gfortran: CONJG: false error message about standard violation

2004-11-19 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-11-19 15:19 --- Confirmed. -- What|Removed |Added Status|UNCONFIRMED |NEW