public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/45005]  New: gfortran.dg/allocate_with_typespec.f90 failed
@ 2010-07-20 13:55 hjl dot tools at gmail dot com
  2010-07-20 13:59 ` [Bug fortran/45005] " hjl dot tools at gmail dot com
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: hjl dot tools at gmail dot com @ 2010-07-20 13:55 UTC (permalink / raw)
  To: gcc-bugs

On Linux/ia32, revision 162325:

http://gcc.gnu.org/ml/gcc-cvs/2010-07/msg00679.html

generated:

FAIL: gfortran.dg/allocate_with_typespec.f90  -O  (test for excess errors)


-- 
           Summary: gfortran.dg/allocate_with_typespec.f90 failed
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: hjl dot tools at gmail dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45005


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug fortran/45005] gfortran.dg/allocate_with_typespec.f90 failed
  2010-07-20 13:55 [Bug fortran/45005] New: gfortran.dg/allocate_with_typespec.f90 failed hjl dot tools at gmail dot com
@ 2010-07-20 13:59 ` hjl dot tools at gmail dot com
  2010-07-20 14:41 ` burnus at gcc dot gnu dot org
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: hjl dot tools at gmail dot com @ 2010-07-20 13:59 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #1 from hjl dot tools at gmail dot com  2010-07-20 13:59 -------
On Linux/x86-64, it caused:

Running target unix/-m32
FAIL: gfortran.dg/allocate_with_typespec.f90  -O  (internal compiler error)
FAIL: gfortran.dg/allocate_with_typespec.f90  -O  (test for excess errors)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45005


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug fortran/45005] gfortran.dg/allocate_with_typespec.f90 failed
  2010-07-20 13:55 [Bug fortran/45005] New: gfortran.dg/allocate_with_typespec.f90 failed hjl dot tools at gmail dot com
  2010-07-20 13:59 ` [Bug fortran/45005] " hjl dot tools at gmail dot com
@ 2010-07-20 14:41 ` burnus at gcc dot gnu dot org
  2010-07-20 23:35 ` sgk at troutmask dot apl dot washington dot edu
  2010-07-21 22:51 ` kargl at gcc dot gnu dot org
  3 siblings, 0 replies; 5+ messages in thread
From: burnus at gcc dot gnu dot org @ 2010-07-20 14:41 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #2 from burnus at gcc dot gnu dot org  2010-07-20 14:41 -------
gfortran.dg/allocate_with_typespec.f90  shows on x86-64-linux (-m64):

gfortran.dg/allocate_with_typespec.f90:25:0: internal compiler error:
Segmentation fault

==11535== Invalid read of size 8
==11535==    at 0x542506: gfc_delete_symtree (symbol.c:2390)
==11535==    by 0x543506: gfc_undo_symbols (symbol.c:2862)
==11535==    by 0x5127E4: decode_statement (parse.c:272)
==11535==    by 0x5143C4: next_statement (parse.c:727)
==11535==    by 0x517EAE: gfc_parse_file (parse.c:4307)
==11535==    by 0x54E447: gfc_be_parse_file (f95-lang.c:236)
==11535==    by 0x83E279: toplev_main (toplev.c:978)
==11535==    by 0x6569B7C: (below main) (in /lib64/libc-2.11.2.so)


-- 

burnus at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
           Keywords|                            |ice-on-valid-code
   Last reconfirmed|0000-00-00 00:00:00         |2010-07-20 14:41:00
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45005


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug fortran/45005] gfortran.dg/allocate_with_typespec.f90 failed
  2010-07-20 13:55 [Bug fortran/45005] New: gfortran.dg/allocate_with_typespec.f90 failed hjl dot tools at gmail dot com
  2010-07-20 13:59 ` [Bug fortran/45005] " hjl dot tools at gmail dot com
  2010-07-20 14:41 ` burnus at gcc dot gnu dot org
@ 2010-07-20 23:35 ` sgk at troutmask dot apl dot washington dot edu
  2010-07-21 22:51 ` kargl at gcc dot gnu dot org
  3 siblings, 0 replies; 5+ messages in thread
From: sgk at troutmask dot apl dot washington dot edu @ 2010-07-20 23:35 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #3 from sgk at troutmask dot apl dot washington dot edu  2010-07-20 23:35 -------
Subject: Re:  gfortran.dg/allocate_with_typespec.f90 failed

On Tue, Jul 20, 2010 at 02:41:01PM -0000, burnus at gcc dot gnu dot org wrote:
> 
> gfortran.dg/allocate_with_typespec.f90  shows on x86-64-linux (-m64):
> 
> gfortran.dg/allocate_with_typespec.f90:25:0: internal compiler error:
> Segmentation fault
> 
> ==11535== Invalid read of size 8
> ==11535==    at 0x542506: gfc_delete_symtree (symbol.c:2390)
> ==11535==    by 0x543506: gfc_undo_symbols (symbol.c:2862)
> ==11535==    by 0x5127E4: decode_statement (parse.c:272)
> ==11535==    by 0x5143C4: next_statement (parse.c:727)
> ==11535==    by 0x517EAE: gfc_parse_file (parse.c:4307)
> ==11535==    by 0x54E447: gfc_be_parse_file (f95-lang.c:236)
> ==11535==    by 0x83E279: toplev_main (toplev.c:978)
> ==11535==    by 0x6569B7C: (below main) (in /lib64/libc-2.11.2.so)
> 

The attached patch restores the order of the old match_type_spec.
It uses gfc_match(" %n ", name) to retrieve the next symbol
from the file and uses strcmp to check against intrinsics
types.  Thus, for allocate_with_typespec.f90, when name=real_type
the comparison fails, and we fall through to the matching for
a derived type by match_derived_type_spec().  I did not
write match_derived_type_spec() and have no idea how it works.
The prolific valgrind output that I see I believe is related
to match_derived_type_spec().  I've also attached the
valgrind log.


------- Comment #4 from sgk at troutmask dot apl dot washington dot edu  2010-07-20 23:35 -------
Created an attachment (id=21272)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21272&action=view)


------- Comment #5 from sgk at troutmask dot apl dot washington dot edu  2010-07-20 23:35 -------
Created an attachment (id=21273)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21273&action=view)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45005


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug fortran/45005] gfortran.dg/allocate_with_typespec.f90 failed
  2010-07-20 13:55 [Bug fortran/45005] New: gfortran.dg/allocate_with_typespec.f90 failed hjl dot tools at gmail dot com
                   ` (2 preceding siblings ...)
  2010-07-20 23:35 ` sgk at troutmask dot apl dot washington dot edu
@ 2010-07-21 22:51 ` kargl at gcc dot gnu dot org
  3 siblings, 0 replies; 5+ messages in thread
From: kargl at gcc dot gnu dot org @ 2010-07-21 22:51 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #6 from kargl at gcc dot gnu dot org  2010-07-21 22:50 -------
I'm closing this PR as FIXED such that I reverted the patch
that caused the problem and re-opened PR fortran/44929.


-- 

kargl at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45005


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2010-07-21 22:51 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-07-20 13:55 [Bug fortran/45005] New: gfortran.dg/allocate_with_typespec.f90 failed hjl dot tools at gmail dot com
2010-07-20 13:59 ` [Bug fortran/45005] " hjl dot tools at gmail dot com
2010-07-20 14:41 ` burnus at gcc dot gnu dot org
2010-07-20 23:35 ` sgk at troutmask dot apl dot washington dot edu
2010-07-21 22:51 ` kargl at gcc dot gnu dot org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).