public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51338] [4.6/4.7 Regression] seg fault in gfc_dep_compare_expr with -O2
Date: Tue, 29 Nov 2011 17:48:00 -0000 [thread overview]
Message-ID: <bug-51338-4-kyOLGH8b8R@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51338-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51338
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
AssignedTo|unassigned at gcc dot |tkoenig at gcc dot gnu.org
|gnu.org |
--- Comment #7 from Thomas Koenig <tkoenig at gcc dot gnu.org> 2011-11-29 17:45:05 UTC ---
(In reply to comment #6)
> The above patch has no new testsuite regressions.
> If someone wants to check and make sure the optimisation(s) that could or were
> being done is still correct, and check this in, feel free to do so.
>
> 1 Hour 40 minutes after bug posted. not bad.....
>
I'll look at it. Thanks for the analysis and the fix!
Thomas
next prev parent reply other threads:[~2011-11-29 17:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 21:10 [Bug fortran/51338] New: " dcb314 at hotmail dot com
2011-11-28 21:49 ` [Bug fortran/51338] " dcb314 at hotmail dot com
2011-11-28 21:59 ` bdavis at gcc dot gnu.org
2011-11-28 22:23 ` bdavis at gcc dot gnu.org
2011-11-28 22:50 ` [Bug fortran/51338] [4.6/4.7 Regression] " dominiq at lps dot ens.fr
2011-11-28 23:10 ` bdavis at gcc dot gnu.org
2011-11-28 23:45 ` bdavis at gcc dot gnu.org
2011-11-29 17:48 ` tkoenig at gcc dot gnu.org [this message]
2011-12-05 14:21 ` rguenth at gcc dot gnu.org
2011-12-05 14:41 ` burnus at gcc dot gnu.org
2011-12-05 16:27 ` jakub at gcc dot gnu.org
2011-12-05 20:12 ` tkoenig at gcc dot gnu.org
2011-12-11 20:06 ` tkoenig at gcc dot gnu.org
2011-12-11 20:11 ` tkoenig 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-51338-4-kyOLGH8b8R@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).