public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51520] [4.6 Regression] ICE in gfortran 4.6.2, x86_64
Date: Tue, 13 Dec 2011 09:19:00 -0000	[thread overview]
Message-ID: <bug-51520-4-yqjnVZn20v@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51520-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-12-13 09:18:04 UTC ---
(In reply to comment #0)
> valgrind output:
> ==18442==    by 0x52BD26: traverse_ns (symbol.c:3333)

(In reply to comment #1)
> The ICE seems to have been fixed on trunk between revisions 180989 (ICE)
> and 181881 (OK).

One possibility could be:

r181232 | burnus | 2011-11-09 20:36:54 +0100 (Wed, 09 Nov 2011) | 7 lines
        * symbol.c (clear_sym_mark, traverse_ns): Remove functions.
        (count_st_nodes, do_traverse_symtree, fill_st_vector): New functions.
        (gfc_traverse_symtree, gfc_traverse_ns): Call do_traverse_symtree.

At least I hope for some smaller patch than the big constructor patch (Rev.
181425).

Dominique: Any chance that you could bisect the 4.7 trunk to find the patch
which fixes the ICE? If not, I can do so later. (You might want to use
--disable-bootstrap --disable-build-poststage1-with-cxx and not building C++ to
speed up the bisecting.)


  parent reply	other threads:[~2011-12-13  9:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12 22:54 [Bug fortran/51520] New: " adrian at llnl dot gov
2011-12-12 23:21 ` [Bug fortran/51520] [4.6 Regression] " dominiq at lps dot ens.fr
2011-12-13  8:49 ` burnus at gcc dot gnu.org
2011-12-13  9:19 ` burnus at gcc dot gnu.org [this message]
2011-12-13 12:55 ` dominiq at lps dot ens.fr
2012-01-12 10:08 ` burnus at gcc dot gnu.org
2012-03-01 15:29 ` jakub at gcc dot gnu.org
2012-11-24 13:14 ` [Bug fortran/51520] [4.6 Regression] ICE in gfortran 4.6.x janus at gcc dot gnu.org
2012-11-24 14:13 ` janus at gcc dot gnu.org
2013-02-15  7:46 ` burnus at gcc dot gnu.org

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-51520-4-yqjnVZn20v@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).