http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31519
--- Comment #13 from bafinney at myrealbox dot com 2010-12-16 21:48:08 UTC ---
For what it is worth, that same code still causes an ICE with MinGW32
F:\brad\fortran\gfortran\tests>gfortran -c -v modbug1.f90
Using built-in specs.
COLLECT_GCC=gfortr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31519
Tobias Burnus changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31519
Kai Tietz changed:
What|Removed |Added
CC||ktietz at gcc dot gnu.org
--- Comment #11 fro
--- Comment #10 from fxcoudert at gcc dot gnu dot org 2010-09-10 21:40
---
*** Bug 45575 has been marked as a duplicate of this bug. ***
--
fxcoudert at gcc dot gnu dot org changed:
What|Removed |Added
-
--- Comment #9 from kargl at gcc dot gnu dot org 2010-01-17 23:06 ---
Is this still a problem on ming32. Can we just drop support
for ming32?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31519
--- Comment #8 from fxcoudert at gcc dot gnu dot org 2009-05-13 19:37
---
I used to see that, but now not any more. Does someone else still see this
happening? And with what testcase?
--
fxcoudert at gcc dot gnu dot org changed:
What|Removed |Adde
--- Comment #7 from fxcoudert at gcc dot gnu dot org 2007-07-13 15:47
---
(In reply to comment #6)
> Bugs where the compiler proper crashes when run under the driver, but not when
> run directly, can often be reproduced by varying the amount of space taken up
> by environment variables,
--- Comment #6 from zackw at panix dot com 2007-04-15 21:22 ---
Bugs where the compiler proper crashes when run under the driver, but not when
run directly, can often be reproduced by varying the amount of space taken up
by environment variables, e.g.
x=
while :; do
x="x$x"
X=$x ./f
--- Comment #5 from tobi at gcc dot gnu dot org 2007-04-15 20:08 ---
(In reply to comment #4)
> (In reply to comment #3)
> > It appears that spurious ICE messages are a general problem with GCC.
>
> Well, it's true that an ICE on invalid code *and* after a sensible error
> message has b
--
fxcoudert at gcc dot gnu dot org changed:
What|Removed |Added
Severity|normal |minor
GCC host triplet||i386-pc-mingw
--- Comment #4 from fxcoudert at gcc dot gnu dot org 2007-04-13 15:19
---
(In reply to comment #3)
> It appears that spurious ICE messages are a general problem with GCC.
Well, it's true that an ICE on invalid code *and* after a sensible error
message has been emitted does not have too
--- Comment #3 from vivekrao4 at yahoo dot com 2007-04-10 23:51 ---
It appears that spurious ICE messages are a general problem with GCC. The site
"Managing Bugs (Bugzilla and the testsuite)" at
http://www.gnu.org/software/gcc/bugs/management.html says
'Bugs with keyword "ice-on-invalid
--- Comment #2 from vivekrao4 at yahoo dot com 2007-04-10 19:38 ---
This bug was discussed in a Feb 2006 thread "suggestion regarding spurious(?)
"internal error" message"
http://gcc.gnu.org/ml/fortran/2006-02/msg00445.html . No one in that thread
said they submitted it to bugzilla.
-
--- Comment #1 from burnus at gcc dot gnu dot org 2007-04-10 07:12 ---
With 4.3.0 20070404/x86_64-unknown-linux-gnu I don't get the ICE - and no
problem is discovered using valgrind.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31519
14 matches
Mail list logo
