* [Bug fortran/36492] incorrect error when compiling
2008-06-10 18:08 [Bug fortran/36492] New: incorrect error when compiling clerman at fuse dot net
@ 2008-06-11 5:37 ` burnus at gcc dot gnu dot org
2008-06-12 13:11 ` clerman at fuse dot net
` (7 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: burnus at gcc dot gnu dot org @ 2008-06-11 5:37 UTC (permalink / raw)
To: gcc-bugs
------- Comment #1 from burnus at gcc dot gnu dot org 2008-06-11 05:36 -------
Can you post a *complete* example? I tried to create a program based on your
single line, but here it simply works.
I tried both (gfortran -v) 4.4.0 20080609 [trunk revision 136577]
and 4.4.0 20080610 [trunk revision 136611] (my x86_64-unknown-linux-gnu
builds).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36492
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug fortran/36492] incorrect error when compiling
2008-06-10 18:08 [Bug fortran/36492] New: incorrect error when compiling clerman at fuse dot net
2008-06-11 5:37 ` [Bug fortran/36492] " burnus at gcc dot gnu dot org
@ 2008-06-12 13:11 ` clerman at fuse dot net
2008-06-13 18:11 ` burnus at gcc dot gnu dot org
` (6 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: clerman at fuse dot net @ 2008-06-12 13:11 UTC (permalink / raw)
To: gcc-bugs
------- Comment #2 from clerman at fuse dot net 2008-06-12 13:11 -------
Subject: Re: incorrect error when compiling
Hello,
Thank you for your quick reply. Attached is an archive, bug2.tar. Unpack it
and invoke the shell script bug2.sh. You should be able to reproduce the
problem. The file bug2.out in the archive shows the results I see.
Thank you very much for your attention.
Yours truly,
Norm Clerman
---- burnus at gcc dot gnu dot org <gcc-bugzilla@gcc.gnu.org> wrote:
>
>
> ------- Comment #1 from burnus at gcc dot gnu dot org 2008-06-11 05:36 -------
> Can you post a *complete* example? I tried to create a program based on your
> single line, but here it simply works.
>
> I tried both (gfortran -v) 4.4.0 20080609 [trunk revision 136577]
> and 4.4.0 20080610 [trunk revision 136611] (my x86_64-unknown-linux-gnu
> builds).
>
>
> --
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36492
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
------- Comment #3 from clerman at fuse dot net 2008-06-12 13:11 -------
Created an attachment (id=15755)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15755&action=view)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36492
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug fortran/36492] incorrect error when compiling
2008-06-10 18:08 [Bug fortran/36492] New: incorrect error when compiling clerman at fuse dot net
2008-06-11 5:37 ` [Bug fortran/36492] " burnus at gcc dot gnu dot org
2008-06-12 13:11 ` clerman at fuse dot net
@ 2008-06-13 18:11 ` burnus at gcc dot gnu dot org
2008-06-13 20:26 ` burnus at gcc dot gnu dot org
` (5 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: burnus at gcc dot gnu dot org @ 2008-06-13 18:11 UTC (permalink / raw)
To: gcc-bugs
------- Comment #4 from burnus at gcc dot gnu dot org 2008-06-13 18:10 -------
OK, I can reproduce it now. Workaround: Replacing -std=f2003 by -std=gnu.
First program, causes an ICE. g95 prints
"Error: Symbol 'max_fld_hed' at (1) has no IMPLICIT type"
------------------------------------------------------
MODULE WinData
IMPLICIT NONE
INTEGER (1), PARAMETER :: MAXFLD = 25_1, MAXHED = 5_1, MAXCHR = 80_1
integer :: i
TYPE TWindowData
CHARACTER (MAX_FLD_HED, 1) :: DWFdHd(MAXFLD) = [(" ", i = 1, MAXFLD)]
END TYPE TWindowData
END MODULE WinData
------------------------------------------------------
Reduced test case - compile with -std=f2003
------------------------------------------------------
INTEGER, PARAMETER :: len = 40
type t
character (len, 1) :: DWFdHd(1) = [(" ", i = 1, 1)]
end type t
end
------------------------------------------------------
Error: The CHARACTER elements of the array constructor at (1) must have the
same length (1/40)
--
burnus at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Keywords| |diagnostic, ice-on-invalid-
| |code
Last reconfirmed|0000-00-00 00:00:00 |2008-06-13 18:10:46
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36492
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug fortran/36492] incorrect error when compiling
2008-06-10 18:08 [Bug fortran/36492] New: incorrect error when compiling clerman at fuse dot net
` (2 preceding siblings ...)
2008-06-13 18:11 ` burnus at gcc dot gnu dot org
@ 2008-06-13 20:26 ` burnus at gcc dot gnu dot org
2008-06-13 20:36 ` d at domob dot eu
` (4 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: burnus at gcc dot gnu dot org @ 2008-06-13 20:26 UTC (permalink / raw)
To: gcc-bugs
------- Comment #5 from burnus at gcc dot gnu dot org 2008-06-13 20:25 -------
> First program, causes an ICE.
Valgrind shows that it fails in decl.c's build_struct:
if (c->ts.type == BT_CHARACTER && !c->pointer && c->initializer)
{
int len = mpz_get_si (c->ts.cl->length->value.integer);
As c->ts.cl->length->value is probably a NULL pointer.
Thus for some reason there is no check whether the length is a specification
expression - or actually in this case it needs to be even an initialization
expression.
Possible starting point for investigations: char_len_param_value
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36492
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug fortran/36492] incorrect error when compiling
2008-06-10 18:08 [Bug fortran/36492] New: incorrect error when compiling clerman at fuse dot net
` (3 preceding siblings ...)
2008-06-13 20:26 ` burnus at gcc dot gnu dot org
@ 2008-06-13 20:36 ` d at domob dot eu
2008-06-18 13:57 ` domob at gcc dot gnu dot org
` (3 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: d at domob dot eu @ 2008-06-13 20:36 UTC (permalink / raw)
To: gcc-bugs
------- Comment #6 from d at domob dot eu 2008-06-13 20:36 -------
Thanks for the additional hint, I'm into this. I've implemented some tests and
am now working on integrating this fix with my pending patch for PR 36517.
When the bogus error is fixed, I'll work on the ICE and hopefully we can fix PR
36517 and this one soon.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36492
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug fortran/36492] incorrect error when compiling
2008-06-10 18:08 [Bug fortran/36492] New: incorrect error when compiling clerman at fuse dot net
` (4 preceding siblings ...)
2008-06-13 20:36 ` d at domob dot eu
@ 2008-06-18 13:57 ` domob at gcc dot gnu dot org
2008-06-20 20:32 ` clerman at fuse dot net
` (2 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: domob at gcc dot gnu dot org @ 2008-06-18 13:57 UTC (permalink / raw)
To: gcc-bugs
------- Comment #7 from domob at gcc dot gnu dot org 2008-06-18 13:56 -------
Committed patch and fixed as rev 136894.
--
domob at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
Target Milestone|--- |4.4.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36492
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug fortran/36492] incorrect error when compiling
2008-06-10 18:08 [Bug fortran/36492] New: incorrect error when compiling clerman at fuse dot net
` (5 preceding siblings ...)
2008-06-18 13:57 ` domob at gcc dot gnu dot org
@ 2008-06-20 20:32 ` clerman at fuse dot net
2008-06-21 8:00 ` domob at gcc dot gnu dot org
2008-06-21 8:44 ` burnus at gcc dot gnu dot org
8 siblings, 0 replies; 10+ messages in thread
From: clerman at fuse dot net @ 2008-06-20 20:32 UTC (permalink / raw)
To: gcc-bugs
------- Comment #8 from clerman at fuse dot net 2008-06-20 20:32 -------
Subject: Re: incorrect error when compiling
Hello,
I'm not sure if I mentioned in my original bug report that I'm downloading
the trunk version for GNU/Linux for 64-bit AMD-compatible processors (x86_64)
processors.
I just downloaded the latest trunk version, which is
GNU Fortran (GCC) 4.4.0 20080616 (experimental) [trunk revision 136838]
Copyright (C) 2008 Free Software Foundation, Inc.
The problem seems to still exist with this release. Do you have any idea when
revision 136894 for this platform will be posted?
Thanks for your assistance.
Yours truly,
Norm Clerman
---- domob at gcc dot gnu dot org <gcc-bugzilla@gcc.gnu.org> wrote:
>
>
> ------- Comment #7 from domob at gcc dot gnu dot org 2008-06-18 13:56 -------
> Committed patch and fixed as rev 136894.
>
>
> --
>
> domob at gcc dot gnu dot org changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|NEW |RESOLVED
> Resolution| |FIXED
> Target Milestone|--- |4.4.0
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36492
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36492
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug fortran/36492] incorrect error when compiling
2008-06-10 18:08 [Bug fortran/36492] New: incorrect error when compiling clerman at fuse dot net
` (6 preceding siblings ...)
2008-06-20 20:32 ` clerman at fuse dot net
@ 2008-06-21 8:00 ` domob at gcc dot gnu dot org
2008-06-21 8:44 ` burnus at gcc dot gnu dot org
8 siblings, 0 replies; 10+ messages in thread
From: domob at gcc dot gnu dot org @ 2008-06-21 8:00 UTC (permalink / raw)
To: gcc-bugs
------- Comment #9 from domob at gcc dot gnu dot org 2008-06-21 07:59 -------
(In reply to comment #8)
> I just downloaded the latest trunk version, which is
>
> GNU Fortran (GCC) 4.4.0 20080616 (experimental) [trunk revision 136838]
> Copyright (C) 2008 Free Software Foundation, Inc.
I committed my patch as rev 136894, so that might be the cause. Otherwise it
could be a problem with 64 bit although I can't imagine that; if so, I'd be
happy to rework the fix.
Daniel
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36492
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug fortran/36492] incorrect error when compiling
2008-06-10 18:08 [Bug fortran/36492] New: incorrect error when compiling clerman at fuse dot net
` (7 preceding siblings ...)
2008-06-21 8:00 ` domob at gcc dot gnu dot org
@ 2008-06-21 8:44 ` burnus at gcc dot gnu dot org
8 siblings, 0 replies; 10+ messages in thread
From: burnus at gcc dot gnu dot org @ 2008-06-21 8:44 UTC (permalink / raw)
To: gcc-bugs
------- Comment #10 from burnus at gcc dot gnu dot org 2008-06-21 08:43 -------
> > I just downloaded the latest trunk version, which is
> > GNU Fortran (GCC) 4.4.0 20080616 (experimental) [trunk revision 136838]
> > Copyright (C) 2008 Free Software Foundation, Inc.
Somehow my x86-64-linux build server failed to create a newer 4.4.0 version
after the 20080616. It should be fixed now and in a few hours today's build
should be available. Sorry for the failure and thanks for finding the problem.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36492
^ permalink raw reply [flat|nested] 10+ messages in thread