public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51522] ICE in gfortran 4.6.2, x86_64
Date: Sat, 04 Feb 2012 00:20:00 -0000	[thread overview]
Message-ID: <bug-51522-4-MUmKCMpbD9@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 #8 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-02-04 00:19:16 UTC ---
> 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. 

Note that I did not say that the segmentation fault was caused by r183681. I
only said that it reappeared at this revision, in the same way I do not think
the problem has been fixed by r183010, but only hidden.

I have tried some versions I have and found that with r183001 there is no
segmentation fault for the reduced test in comment #4, only the original test
gives it, while for r179630 both give the segmentation fault. Note that I do
not get any segmentation fault for both tests on powerpc-apple-darwin9.


  parent reply	other threads:[~2012-02-04  0:20 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
2012-02-04  0:20 ` dominiq at lps dot ens.fr [this message]
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-MUmKCMpbD9@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).