--- Comment #7 from pault at gcc dot gnu dot org 2008-01-20 08:44 ---
Fixed on trunk
Paul
--
pault at gcc dot gnu dot org changed:
What|Removed |Added
Status
--- Comment #6 from pault at gcc dot gnu dot org 2008-01-20 08:23 ---
Subject: Bug 34785
Author: pault
Date: Sun Jan 20 08:22:56 2008
New Revision: 131675
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=131675
Log:
2008-01-20 Paul Thomas <[EMAIL PROTECTED]>
PR fortran/
--- Comment #5 from pault at gcc dot gnu dot org 2008-01-18 09:33 ---
(In reply to comment #4)
Sorry, the above is the fix for PR34784.
This one is fixed by:
In trans-array.c (gfc_add_loop_ss_code)
case GFC_SS_CONSTRUCTOR:
if (ss->expr->ts.type == BT_CHARACTER
--- Comment #4 from pault at gcc dot gnu dot org 2008-01-18 09:22 ---
(In reply to comment #3)
> I have a fix for this that I will apply as "obvious" overnight (in the EU,
> that
> is:))
> Paul
except that it caused a FAIL on one platform and, on another, the testsuite
hung!!! Anyw
--- Comment #3 from pault at gcc dot gnu dot org 2008-01-17 15:33 ---
I have a fix for this that I will apply as "obvious" overnight (in the EU, that
is:))
Paul
--
pault at gcc dot gnu dot org changed:
What|Removed |Added
-
--- Comment #2 from pault at gcc dot gnu dot org 2008-01-16 08:00 ---
(In reply to comment #1)
It is sufficient that BA_T is referenced in tests; eg. by PRINT *, BA_T for the
problem to go away. Thus the problem is that the symbol is not being set as
referenced. I will try to find out
--- Comment #1 from burnus at gcc dot gnu dot org 2008-01-14 23:04 ---
The failing assert is:
/* Complex character array constructors should have been taken care of
and not end up here. */
gcc_assert (ss->string_length);
Reduced test:
MODULE o_TYPE_DEFS
--
burnus at gcc dot gnu dot org changed:
What|Removed |Added
OtherBugsDependingO||32834
nThis||
St
