[Bug target/20820] -mlong-double-128 arithmetic error

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 06:22 --- Fixed already in 4.0.0, not a regression so closing as fixed, there is another bug about this too. -- What|Removed |Added

[Bug c++/20818] internal compiler error

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 06:26 --- This is invalid code. See PR 8788 which I am marking this as a dup of. *** This bug has been marked as a duplicate of 8788 *** -- What|Removed |Added

[Bug inline-asm/8788] ICE in emit_move_insn, at expr.c:3089

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 06:26 --- *** Bug 20818 has been marked as a duplicate of this bug. *** -- What|Removed |Added

[Bug fortran/20821] New: gfortran hangs indefinitely

2005-04-08 Thread jvdelisle at verizon dot net
When compiling the following code gfortran hangs spinning cpu cycles with no error messages given. See attachment. -- Summary: gfortran hangs indefinitely Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority:

[Bug fortran/20821] gfortran hangs indefinitely

2005-04-08 Thread jvdelisle at verizon dot net
--- Additional Comments From jvdelisle at verizon dot net 2005-04-08 06:43 --- Created an attachment (id=8561) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8561action=view) Attached file hangs gfortran Using gcc version 4.1.0 20050408 (experimental) Invoked with -c -- http

[Bug fortran/20821] gfortran hangs indefinitely

2005-04-08 Thread jvdelisle at verizon dot net
--- Additional Comments From jvdelisle at verizon dot net 2005-04-08 06:47 --- Created an attachment (id=8562) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8562action=view) Module for attachment in #1 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20821

[Bug fortran/20821] gfortran hangs indefinitely

2005-04-08 Thread jvdelisle at verizon dot net
--- Additional Comments From jvdelisle at verizon dot net 2005-04-08 06:49 --- I will attempt to reduce this. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20821

[Bug target/20819] Enable -mlong_calls for IA64 to use brl.call

2005-04-08 Thread pinskia at gcc dot gnu dot org
-- What|Removed |Added GCC build triplet|ia64-redhat-linux | GCC host triplet|ia64-redhat-linux | GCC target triplet|ia64-redhat-linux

[Bug target/20819] Enable -mlong-call for IA64 to use brl.call

2005-04-08 Thread pinskia at gcc dot gnu dot org
-- What|Removed |Added Summary|Enable -mlong_calls for IA64|Enable -mlong-call for IA64 |to use brl.call |to use brl.call

[Bug fortran/13082] Function entries and entries with alternate returns not implemented

2005-04-08 Thread fca at mail dot cern dot ch
--- Additional Comments From fca at mail dot cern dot ch 2005-04-08 07:14 --- Subject: Re: Function entries and entries with alternate returns not implemented Dear All, I think that the tone of the conversation is evolving in the wrong direction (I might have been partially

[Bug c++/20812] contextual overload resolution failure for a member name found in two base classes

2005-04-08 Thread SWElef at post dot sk
--- Additional Comments From SWElef at post dot sk 2005-04-08 07:33 --- Well, if we speak about other compilers, MSVC++ Toolkit 2003 supports my view on the first snippet and emits an ICE on the second. And the behaviour of Comeau Online is pretty irrelevant as it fails deduction even

[Bug fortran/13082] Function entries and entries with alternate returns not implemented

2005-04-08 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-04-08 07:36 --- Subject: Re: Function entries and entries with alternate returns not implemented You wrote (in bugzilla): - We tried out the designed successor and found it very immature. In fact it is not even

[Bug ada/20822] New: makeinfo cannot process gnat_ugn_unw.texi

2005-04-08 Thread rolf dot ebert dot gcc at gmx dot de
when bootstrapping on Windows (mingw/msys) the documentation is not generated. Makeinfo stops with the complaint: $ cat -v make.err doc/gnat_ugn_unw.texi:92: Unknown index `fn' and/or `cp^M' in @synindex. ./doc/gnat_ugn_unw.texi:11211: Cross reference to nonexistent node `Alternative^M File

[Bug fortran/20821] gfortran hangs indefinitely

2005-04-08 Thread jvdelisle at verizon dot net
--- Additional Comments From jvdelisle at verizon dot net 2005-04-08 08:15 --- Created an attachment (id=8563) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8563action=view) Reduced case The attached file is a reduced case that reproduces this hang. See comments for edits that

[Bug libstdc++/20758] operator-(const T, const complexT) vs operator-(const complexT, const complexT)

2005-04-08 Thread kreckel at ginac dot de
--- Additional Comments From kreckel at ginac dot de 2005-04-08 08:23 --- (In reply to comment #17) Yes, I was referring to the draft N481, but actually N490 is more recent (no changes in the area at issue) both are available from

[Bug java/20768] Bytecode - native code doesn't handle exception properly

2005-04-08 Thread aph at gcc dot gnu dot org
-- What|Removed |Added AssignedTo|unassigned at gcc dot gnu |aph at gcc dot gnu dot org |dot org | Status|NEW

[Bug target/20446] [4.0/4.1 Regression] invalid assembly with -gstabs+

2005-04-08 Thread ebotcazou at gcc dot gnu dot org
--- Additional Comments From ebotcazou at gcc dot gnu dot org 2005-04-08 08:53 --- Thanks for confirming. -- What|Removed |Added Status|RESOLVED

[Bug libstdc++/20758] operator-(const T, const complexT) vs operator-(const complexT, const complexT)

2005-04-08 Thread pcarlini at suse dot de
--- Additional Comments From pcarlini at suse dot de 2005-04-08 09:51 --- Yes, I agree that things seem rather crazy, indeed the behavior that you reported seemed crazy in the first place. I think all of this is a matter of compromises: when zero is involved the signedness turns out to

[Bug libstdc++/20823] New: frv-unknown-elf doesn't build: GCC_NO_EXECUTABLES unexpanded

2005-04-08 Thread hp at gcc dot gnu dot org
With LAST_UPDATED Tue Mar 29 15:04:38 UTC 2005 and using geoffk's btest-gcc.sh script, this target built with reasonable test-results. with LAST_UPDATED Thu Apr 7 18:10:49 UTC 2005, I see this in the build log: ... make[5]: Leaving directory

[Bug fortran/20824] New: Legal code involving if statement does not compile

2005-04-08 Thread federico dot carminati at cern dot ch
Legal code does not compile PROGRAM BUG I=10 IF(I.GT.10) IF(I) 10, 20, 30 10 CONTINUE 20 CONTINUE 30 CONTINUE END [/Users/fca] /opt/gcc-4_0/bin/gfortran -c bugf00.f In file bugf00.f:3 IF(I.GT.10) IF(I) 10, 20, 30

[Bug fortran/20824] Legal code involving if statement does not compile

2005-04-08 Thread federico dot carminati at cern dot ch
-- What|Removed |Added CC||alfredo dot ferrari at cern ||dot ch

[Bug fortran/20824] Legal code involving if statement does not compile

2005-04-08 Thread federico dot carminati at cern dot ch
-- What|Removed |Added CC||Fons dot Rademakers at cern ||dot ch

[Bug fortran/17229] parser confused by arithmetic if inside an if

2005-04-08 Thread cvs-commit at gcc dot gnu dot org
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-04-08 10:57 --- Subject: Bug 17229 CVSROOT:/cvs/gcc Module name:gcc Branch: gcc-4_0-branch Changes by: [EMAIL PROTECTED] 2005-04-08 10:56:54 Modified files: gcc/fortran:

[Bug fortran/17229] parser confused by arithmetic if inside an if

2005-04-08 Thread cvs-commit at gcc dot gnu dot org
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-04-08 10:57 --- Subject: Bug 17229 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-04-08 10:57:00 Modified files: gcc/fortran: ChangeLog match.c

[Bug ada/20548] [4.1 Regression] ACATS c52103x segfault at runtime on x86_64

2005-04-08 Thread laurent at guerby dot net
--- Additional Comments From laurent at guerby dot net 2005-04-08 10:58 --- Same failure on 4.1.0 20050405 (experimental) powerpc64-suse-linux-gnu http://gcc.gnu.org/ml/gcc-testresults/2005-04/msg00414.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20548

[Bug fortran/17229] parser confused by arithmetic if inside an if

2005-04-08 Thread fxcoudert at gcc dot gnu dot org
--- Additional Comments From fxcoudert at gcc dot gnu dot org 2005-04-08 11:11 --- Fixed. -- What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug fortran/19292] [meta-bug] g77 features lacking in gfortran

2005-04-08 Thread fxcoudert at gcc dot gnu dot org
-- Bug 19292 depends on bug 17229, which changed state. Bug 17229 Summary: parser confused by arithmetic if inside an if http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17229 What|Old Value |New Value

[Bug fortran/20825] New: gfortran does not support Hollerith

2005-04-08 Thread federico dot carminati at cern dot ch
The following program does not compile with gfortran PROGRAM BUG DATA I / 4HCIAO / PRINT '(A)', I END [/Users/fca] /opt/gcc-4_0/bin/gfortran -c bugf00.f In file bugf00.f:2 DATA I / 4HCIAO / 1

[Bug c++/20826] New: 4.0 regression: excessive compiler resource usage

2005-04-08 Thread dwmw2 at infradead dot org
Compiling the attached file with '-fno-enforce-eh-specs -O2' on a 450MHz G4 with gcc 3.4 takes 30 seconds. Compiling it with gcc 4 on a 1.3GHz G4 takes a number of hours before failing: cc1plus: out of memory allocating 1643995136 bytes after a total of 94982144 bytes This are both

[Bug c++/20826] 4.0 regression: excessive compiler resource usage

2005-04-08 Thread dwmw2 at infradead dot org
--- Additional Comments From dwmw2 at infradead dot org 2005-04-08 11:34 --- Created an attachment (id=8564) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8564action=view) offending source file -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20826

[Bug fortran/20824] Legal code involving if statement does not compile

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 11:43 --- This is a dup of bug 17229 which just got fixed today. *** This bug has been marked as a duplicate of 17229 *** -- What|Removed |Added

[Bug fortran/17229] parser confused by arithmetic if inside an if

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 11:43 --- *** Bug 20824 has been marked as a duplicate of this bug. *** -- What|Removed |Added

[Bug c++/20826] 4.0 regression: excessive compiler resource usage

2005-04-08 Thread pinskia at gcc dot gnu dot org
-- What|Removed |Added Severity|critical|normal Keywords||compile-time-hog, memory-hog

[Bug fortran/20825] gfortran does not support Hollerith

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 11:46 --- *** This bug has been marked as a duplicate of 16531 *** -- What|Removed |Added

[Bug fortran/16531] [gfortran] Hollerith Data not supported

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 11:47 --- *** Bug 20825 has been marked as a duplicate of this bug. *** -- What|Removed |Added

[Bug middle-end/20826] 4.0 regression: excessive compiler resource usage

2005-04-08 Thread pinskia at gcc dot gnu dot org
-- What|Removed |Added Component|c++ |middle-end http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20826

[Bug ada/20822] makeinfo cannot process gnat_ugn_unw.texi

2005-04-08 Thread ericw at evcohs dot com
--- Additional Comments From ericw at evcohs dot com 2005-04-08 11:48 --- I got this same error as Rolf did, building an AVR cross GCC with Ada on MinGW. Could someone with more permissions be willing to set the Status as NEW? Eric Weddington --

[Bug fortran/20827] New: Compiler gets stuck in loop on valid code

2005-04-08 Thread paulthomas2 at wanadoo dot fr
This extract from the code of Guglielmo Pasa causes GNU Fortran 95 (GCC 4.1.0 20050401 (experimental)) to go into an infinite loop. Reducing the number of optional arguments or changing LEN(WHAT) to LEN=10, for example, stop the infinite loop. SUBROUTINE CQUERY(WHAT,OUI,NON)

[Bug fortran/20827] Compiler gets stuck in loop on valid code

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 11:55 --- *** This bug has been marked as a duplicate of 20821 *** -- What|Removed |Added

[Bug fortran/20821] gfortran hangs indefinitely

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 11:55 --- *** Bug 20827 has been marked as a duplicate of this bug. *** -- What|Removed |Added

[Bug fortran/20821] gfortran hangs indefinitely

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 11:55 --- Confirmed. -- What|Removed |Added Status|UNCONFIRMED |NEW

[Bug middle-end/20826] 4.0 regression: excessive compiler resource usage

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 12:06 --- Compile time does seem high. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20826

[Bug fortran/20828] New: gfortran seems confused by character equivalence

2005-04-08 Thread federico dot carminati at cern dot ch
The following valid code fails to compile PROGRAM BUG CHARACTER CQALLC*1, CQLETT(1)*1 EQUIVALENCE (CQLETT(1),CQALLC(1:1)) END [/Users/fca] /opt/gcc-4_0/bin/gfortran -I $ALICE/geant3/minicern -c bugf00.F 21 | more In file bugf00.F:5 END

[Bug rtl-optimization/20413] VOIDmode LABEL_REFs are generated

2005-04-08 Thread amylaar at gcc dot gnu dot org
--- Additional Comments From amylaar at gcc dot gnu dot org 2005-04-08 12:19 --- I have removed the build keyword because I have found an ugly hack - wildcard splitters - that allow the sh64-elf build to proceed despite of this bug. -- What|Removed

[Bug fortran/20828] gfortran seems confused by character equivalence

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 12:20 --- *** This bug has been marked as a duplicate of 18833 *** -- What|Removed |Added

[Bug fortran/18833] ICE 'missing spec' on integer/char equivalence

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 12:20 --- *** Bug 20828 has been marked as a duplicate of this bug. *** -- What|Removed |Added

[Bug fortran/18833] ICE 'missing spec' on integer/char equivalence

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 12:22 --- Even though the code listed in comment #0 is F90/F95, you can generate a f77 code which causes the same problem like so (from PR 20828): PROGRAM BUG CHARACTER CQALLC*1, CQLETT(1)*1

[Bug fortran/20829] New: Internal compiler error with valid code

2005-04-08 Thread federico dot carminati at cern dot ch
The following code causes an internal compiler error. I could not obtain any further reduction of the case SUBROUTINE BUG DIMENSION IR(10), A(10,10) #include fact.inc RETURN END file fact.inc DO 144J = 1, N DO 143 K = JP1, N DO 141

[Bug fortran/20829] Internal compiler error with valid code

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 12:56 --- Confirmed, I think this is a dup of bug 19195 but any slight changes to the preprocessed source will cause the ICE to go away. -- What|Removed |Added

[Bug debug/20830] New: bad debug info for static nested struct with virtual function

2005-04-08 Thread kjd at duda dot org
Suppose foo.cpp contains this: void foo() { static struct { struct { virtual void func() {} } test1; } test2; } If you compile this with gcc-3.4.2 and invoke gdb: g++ -g -c foo.cpp gdb foo.o gdb dies with:

[Bug debug/20830] bad debug info for static nested struct with virtual function

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 13:31 --- What version of gdb are you using? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20830

[Bug c++/19317] [4.1 Regression] removing a temporary return value when we cannot

2005-04-08 Thread pluto at pld-linux dot org
--- Additional Comments From pluto at pld-linux dot org 2005-04-08 13:33 --- (In reply to comment #15) thats the same issue like the konqueror crash which I couldn't find a workaround for in gcc either. (gdb) bt #0 ~QIconSet (this=0x8209614) at qshared.h:50 ~QIconSet

[Bug debug/20830] bad debug info for static nested struct with virtual function

2005-04-08 Thread kjd at duda dot org
--- Additional Comments From kjd at duda dot org 2005-04-08 13:35 --- (In reply to comment #1) What version of gdb are you using? Sorry for forgetting the gdb version number. I get identical behavior from both GNU gdb Red Hat Linux (6.1post- 1.20040607.41rh) and GNU gdb 6.3 (built

[Bug debug/20830] [3.3/3.4 Regression] bad debug info for static nested struct with virtual function

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 13:39 --- Hmm, 3.5.0 20040909 works but 3.4.0 does not. This is weird, I don't know what fixed this or even what broke it either. And I don't know if gdb is correct or gcc. -- What|Removed

[Bug c++/20831] New: ICE: SEGV with -fmudflap

2005-04-08 Thread green at redhat dot com
$ g++ -O2 -fmudflap -c link.ii ../../../gcc/libjava/link.cc: In static member function ‘static void _Jv_Linker::make_vtable(java::lang::Class*)’: ../../../gcc/libjava/link.cc:63: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate.

[Bug libfortran/16436] gfortran TL edit descriptor failure - test f77-edit-t-in.f

2005-04-08 Thread fxcoudert at gcc dot gnu dot org
-- What|Removed |Added AssignedTo|fxcoudert at gcc dot gnu dot|unassigned at gcc dot gnu |org |dot org Status|ASSIGNED

[Bug c++/20831] ICE: SEGV with -fmudflap

2005-04-08 Thread green at redhat dot com
--- Additional Comments From green at redhat dot com 2005-04-08 13:46 --- Created an attachment (id=8565) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8565action=view) Preprocessed source for test case (trimmed down) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20831

[Bug c++/20831] ICE: SEGV with -fmudflap

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 13:47 --- I would not doubt that this is just a dup of bug 19266. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20831

[Bug c++/20831] ICE: SEGV with -fmudflap

2005-04-08 Thread pinskia at gcc dot gnu dot org
-- What|Removed |Added Attachment #8565|application/octet-stream|text/plain mime type||

[Bug c++/20831] ICE: SEGV with -fmudflap

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 13:50 --- *** This bug has been marked as a duplicate of 19266 *** -- What|Removed |Added

[Bug other/19266] [mudflap] ICE when compiling with -fmudflap -O

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 13:50 --- *** Bug 20831 has been marked as a duplicate of this bug. *** -- What|Removed |Added

[Bug libstdc++/20758] operator-(const T, const complexT) vs operator-(const complexT, const complexT)

2005-04-08 Thread gdr at integrable-solutions dot net
--- Additional Comments From gdr at integrable-solutions dot net 2005-04-08 14:15 --- Subject: Re: operator-(const T, const complexT) vs operator-(const complexT, const complexT) kreckel at ginac dot de [EMAIL PROTECTED] writes: | (In reply to comment #11) | I think we need more

[Bug libstdc++/20758] operator-(const T, const complexT) vs operator-(const complexT, const complexT)

2005-04-08 Thread gdr at integrable-solutions dot net
--- Additional Comments From gdr at integrable-solutions dot net 2005-04-08 14:20 --- Subject: Re: operator-(const T, const complexT) vs operator-(const complexT, const complexT) kreckel at ginac dot de [EMAIL PROTECTED] writes: | (In reply to comment #15) | Well, Richard,

[Bug fortran/13257] Error instead of warning for missing comma in format string

2005-04-08 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-08 14:27 --- I have a fix which I am testing right now. -- What|Removed |Added

[Bug c++/19404] [4.0 Regression] anonymous types and templates and rejecting valid code

2005-04-08 Thread lars at trolltech dot com
--- Additional Comments From lars at trolltech dot com 2005-04-08 14:36 --- Hi Mark, (In reply to comment #3) This code is invalid. The use of requires the instantiation of the declaration of the overloaded operator, but that instantiation fails because one of the template

[Bug libfortran/20832] New: Segfault in SUM

2005-04-08 Thread fxcoudert at gcc dot gnu dot org
Segfault in libgfortran on both MinGW and i686-linux: $ cat fc014.f90 ! Original bug-report by Walt Brainerd, The Fortran Company integer,dimension(1,1) :: mis1 = 1 logical,dimension(1,1) :: ml2 = .true. integer,dimension(1) :: s ! s = sum(mis1,dim=1,mask=ml2) ! This line works print

[Bug libfortran/18495] Intrinisc function SPREAD is broken

2005-04-08 Thread fxcoudert at gcc dot gnu dot org
--- Additional Comments From fxcoudert at gcc dot gnu dot org 2005-04-08 15:28 --- Yet another SPREAD problem: ! Original bug-report by Walt Brainerd, The Fortran Company integer,dimension(2) :: mi1 = 1 integer,dimension(1,1) :: s s = spread(mi1,1,2) end I agree those

[Bug c++/19404] [4.0 Regression] anonymous types and templates and rejecting valid code

2005-04-08 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-04-08 15:34 --- Subject: Re: [4.0 Regression] anonymous types and templates and rejecting valid code lars at trolltech dot com wrote: --- Additional Comments From lars at trolltech dot com 2005-04-08 14:36 ---

[Bug fortran/20833] New: LEN of a null slice and temporaries don't mix up well

2005-04-08 Thread fxcoudert at gcc dot gnu dot org
$ cat fc019.f90 ! Original bug-report submitted by Walt Brainerd, The Fortran Company character(len=128) :: ASCII = ' ' ! This works integer i i = len (ASCII(1:0)) print *, i ! This works too print *, len (ASCII(1:2)) ! This fails print *, len (ASCII(1:0)) end $ gfc fc019.f90

[Bug fortran/20834] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' COMMON /BLOCKA/ A,B,C COMMON /BLOCKB/ D,E,F EQUIVALENCE(B,E) END -- Summary: error needed Product: gcc Version: 4.1.0 Status:

[Bug fortran/20835] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' REAL :: A REAL, TARGET :: B EQUIVALENCE(A,B) END -- Summary: error needed Product: gcc Version: 4.1.0 Status: UNCONFIRMED

[Bug fortran/20836] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' MODULE TEST PRIVATE TYPE info_type INTEGER :: value END TYPE info_type TYPE all_type TYPE(info_type) :: info END TYPE PUBLIC :: all_type END MODULE END --

[Bug fortran/20837] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' integer, parameter, public :: i=1 END -- Summary: error needed Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity:

[Bug fortran/20838] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' INTEGER, PARAMETER, DIMENSION(3) :: subs=(/1,3,2/) INTEGER, DIMENSION(3), TARGET :: vals INTEGER, POINTER, DIMENSION(:) :: ptr ptr=vals(subs) END -- Summary: error needed

[Bug fortran/20839] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' doi: DO 111 i=1,3 111 continue ! requires END DO doi END -- Summary: error needed Product: gcc Version: 4.1.0 Status: UNCONFIRMED

[Bug fortran/20840] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' INTEGER, PARAMETER :: subs(3)=(/1,3,2/) CHARACTER, DIMENSION(3) :: file write(file(subs),*) 0 END -- Summary: error needed Product: gcc Version:

[Bug fortran/20841] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' INTEGER, PARAMETER :: subs(3)=(/1,3,2/) CHARACTER, DIMENSION(3) :: file write(file(subs),*) 0 END -- Summary: error needed Product: gcc Version:

[Bug fortran/20842] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' WRITE(UNIT=6,END=999) 0 999 CONTINUE END -- Summary: error needed Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity:

[Bug fortran/20843] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' CHARACTER :: a(3) WRITE(a) 0 ! no unformatted on internal file END -- Summary: error needed Product: gcc Version: 4.1.0 Status:

[Bug fortran/20844] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' WRITE(6,ADVANCE='NO') 0 END -- Summary: error needed Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal

[Bug fortran/20845] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' MODULE T1 TYPE init_type integer :: i=1 END TYPE init_type TYPE(init_type) :: x END MODULE T1 END -- Summary: error needed Product: gcc

[Bug fortran/20846] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' INQUIRE(FILE=TEST,UNIT=7,RECL=I) END -- Summary: error needed Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity:

[Bug fortran/20847] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' INTEGER, SAVE :: X COMMON /COM/ X END -- Summary: error needed Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity:

[Bug fortran/20848] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' INTEGER, PARAMETER, SAVE :: X=0 END -- Summary: error needed Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal

[Bug fortran/20849] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' REAL, EXTERNAL :: X=0 END -- Summary: error needed Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal

[Bug fortran/20850] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' CHARACTER(LEN=10) :: B CHARACTER :: A EQUIVALENCE (A,B(1:-1)) END -- Summary: error needed Product: gcc Version: 4.1.0 Status:

[Bug fortran/20851] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' MODULE TT CONTAINS ELEMENTAL REAL FUNCTION two(N) INTEGER, INTENT(IN) :: N INTEGER, DIMENSION(N) :: scr END FUNCTION END MODULE END -- Summary: error

[Bug fortran/20852] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' RECURSIVE FUNCTION TEST() CHARACTER(LEN=*) :: TEST END FUNCTION END -- Summary: error needed Product: gcc Version: 4.1.0 Status:

[Bug fortran/20853] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' MODULE TEST TYPE init INTEGER :: I=0 END TYPE init CONTAINS SUBROUTINE try(A) TYPE(init), DIMENSION(*), INTENT(OUT) :: A END SUBROUTINE try END MODULE TEST END --

[Bug fortran/20854] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' MODULE TEST TYPE tt INTEGER :: I END TYPE tt PUBLIC :: try PRIVATE :: tt CONTAINS SUBROUTINE try(A) TYPE(tt) :: A END SUBROUTINE try END MODULE TEST END -- Summary:

[Bug fortran/20855] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' 0 CONTINUE END -- Summary: error needed Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority:

[Bug fortran/20856] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' FUNCTION X() RESULT(Y) REAL, SAVE :: Y END FUNCTION X END -- Summary: error needed Product: gcc Version: 4.1.0 Status: UNCONFIRMED

[Bug fortran/20857] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' MODULE TEST CONTAINS SUBROUTINE TT(I) INTEGER, INTENT(inOUT) :: I END SUBROUTINE TT END MODULE TEST USE TEST CALL TT(0) END -- Summary: error needed

[Bug fortran/20858] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' INTEGER, POINTER :: I REAL, POINTER :: A A=NULL(I) END -- Summary: error needed Product: gcc Version: 4.1.0 Status: UNCONFIRMED

[Bug fortran/20859] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' INTEGER :: I(3)=(/1,3,2/),J(3) CALL TT(J(I)) CONTAINS SUBROUTINE TT(K) INTEGER, INTENT(OUT) :: K(3) END SUBROUTINE END -- Summary: error needed Product:

[Bug fortran/20860] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' TYPE data_type SEQUENCE INTEGER :: I=7 END TYPE data_type INTEGER :: J TYPE(data_type) :: dd COMMON /COM/ J EQUIVALENCE(dd,J) END -- Summary: error needed

[Bug fortran/20861] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' CALL DD(TT) CONTAINS SUBROUTINE DD(F) INTERFACE SUBROUTINE F(X) REAL :: X END SUBROUTINE F END INTERFACE END SUBROUTINE DD SUBROUTINE TT(X) REAL :: X END SUBROUTINE

[Bug fortran/20862] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' MODULE TT 10 FORMAT(I8) END MODULE TT END -- Summary: error needed Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity:

[Bug fortran/20863] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' MODULE TT TYPE node_type TYPE(node_type), POINTER :: next=null() END TYPE CONTAINS PURE FUNCTION give_next(node) TYPE(node_type), POINTER :: node TYPE(node_type),

[Bug fortran/20864] New: error needed

2005-04-08 Thread jv244 at cam dot ac dot uk
The following is non-standard and the compiler should probably generate a warning/error with '-pedantic -std=f95' MODULE T1 TYPE data_type SEQUENCE ! private causes the types in T1 and T2 to be different 4.4.2 PRIVATE INTEGER :: I END TYPE END MODULE MODULE T2 TYPE data_type SEQUENCE

  1   2   3   >