--- Comment #13 from pault at gcc dot gnu dot org 2006-08-30 05:33 ---
Fixed on trunk and 4.1
Paul
--
pault at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #12 from pault at gcc dot gnu dot org 2006-08-30 05:19 ---
Subject: Bug 24866
Author: pault
Date: Wed Aug 30 05:19:34 2006
New Revision: 116579
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=116579
Log:
2006-08-30 Paul Thomas <[EMAIL PROTECTED]>
PR fortran
--- Comment #11 from pault at gcc dot gnu dot org 2006-08-30 05:19 ---
Subject: Bug 24866
Author: pault
Date: Wed Aug 30 05:18:36 2006
New Revision: 116578
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=116578
Log:
2006-08-30 Paul Thomas <[EMAIL PROTECTED]>
PR fortran
--- Comment #10 from patchapp at dberlin dot org 2006-08-20 07:45 ---
Subject: Bug number PR24866
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/2006-08/msg00719.html
--
http://gcc.gnu.org/bugzilla/s
--- Comment #9 from patchapp at dberlin dot org 2006-08-20 06:01 ---
Subject: Bug number PR24866
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/2006-08/msg00711.html
--
http://gcc.gnu.org/bugzilla/sh
--- Comment #8 from pault at gcc dot gnu dot org 2006-08-19 16:54 ---
Created an attachment (id=12098)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12098&action=view)
A fix for the PR and a testsuite entry
The problem turned out to be in parse.c(gfc_fixup_sibling_symbols), which
--- Comment #7 from pault at gcc dot gnu dot org 2006-08-19 12:32 ---
Yes, the problem is as I thought; rename the dummy and the external procedure,
say to str1, and the module compiles fine. It also compiles if the order of
the subroutines is changed. These are symptomatic of the symb
--- Comment #6 from pault at gcc dot gnu dot org 2006-08-19 05:49 ---
> I know you're on vacation, Paul, but I think what looks troubling to us would
> look trivial to you, friendly as you are with the module code in gfortran!
>
I'll have a look today - I am in the midst of a triage of
--- Comment #5 from fxcoudert at gcc dot gnu dot org 2006-07-24 21:30
---
This one is still here, segfaulting or giving incorrect error message depending
on the optimization level used for building the front-end.
We enter write_symbol1 with p->u.rsym->sym.name = "sub_module", we go to
--- Comment #4 from fxcoudert at gcc dot gnu dot org 2006-05-21 20:37
---
Why is this code invalid? (the keywork ice-on-invalid-code is set)
No error is reported with Sun, Intel and g95.
--
fxcoudert at gcc dot gnu dot org changed:
What|Removed |
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-01-27 20:46 ---
I now get:
end module test_module
1
Internal Error at (1):
write_symbol(): bad module symbol 'UCS-2BE//'
--
pinskia at gcc dot gnu dot org changed:
What|Removed
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-01-03 17:07 ---
Not PPC specific.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
GCC build triple
--- Comment #1 from pinskia at gcc dot gnu dot org 2005-11-15 04:21 ---
Confirmed, maybe related to PR 20892.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
---
13 matches
Mail list logo
