public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51522] ICE in gfortran 4.6.2, x86_64
Date: Fri, 03 Feb 2012 22:36:00 -0000	[thread overview]
Message-ID: <bug-51522-4-FgTREhnhnp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51522-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Janne Blomqvist <jb at gcc dot gnu.org> 2012-02-03 22:36:13 UTC ---
(In reply to comment #6)
> If I try the example of comment 4 with the line break before "&" undone and
> using the newest 4.7 trunk (clean build), I see in valgrind:
> 
> ==14154== Invalid read of size 4
> ==14154==    at 0x52D345: resolve_symbol (resolve.c:10559)
> ==14154==    by 0x54131F: do_traverse_symtree (symbol.c:3385)
> ==14154==    by 0x530093: resolve_types (resolve.c:13859)
> ==14154==    by 0x5243DB: gfc_resolve (resolve.c:13959)

Yes, I saw the same thing. But, as I didn't see any relation between
resolve.c:10559 and the r183681 patch, I assumed this was something which was
present before and didn't investigate further. 

Also, looking at the r183681 patch itself at
http://gcc.gnu.org/ml/fortran/2012-01/msg00255.html, I find it difficult to see
how it can cause any problems (*knocking on wood*).


  parent reply	other threads:[~2012-02-03 22:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12 23:09 [Bug fortran/51522] New: " adrian at llnl dot gov
2011-12-12 23:25 ` [Bug fortran/51522] " dominiq at lps dot ens.fr
2012-01-09 13:30 ` burnus at gcc dot gnu.org
2012-01-09 13:40 ` dominiq at lps dot ens.fr
2012-01-31 16:11 ` dominiq at lps dot ens.fr
2012-02-02 19:08 ` jb at gcc dot gnu.org
2012-02-03 10:50 ` burnus at gcc dot gnu.org
2012-02-03 22:36 ` jb at gcc dot gnu.org [this message]
2012-02-04  0:20 ` dominiq at lps dot ens.fr
2012-02-05 21:04 ` jb at gcc dot gnu.org
2015-10-10 12:57 ` dominiq at lps dot ens.fr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-51522-4-FgTREhnhnp@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).