public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/59387] [4.9 Regression] wrong code (hangs) at -Os on x86_64-linux-gnu
Date: Thu, 19 Dec 2013 11:01:00 -0000 [thread overview]
Message-ID: <bug-59387-4-rdVAJJvr7U@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59387-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59387
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
Summary|wrong code (hangs) at -Os |[4.9 Regression] wrong code
|on x86_64-linux-gnu |(hangs) at -Os on
| |x86_64-linux-gnu
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r196792. Looking at it.
next prev parent reply other threads:[~2013-12-19 11:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 18:41 [Bug tree-optimization/59387] New: " su at cs dot ucdavis.edu
2013-12-05 10:57 ` [Bug tree-optimization/59387] " rguenth at gcc dot gnu.org
2013-12-19 11:01 ` jakub at gcc dot gnu.org [this message]
2013-12-19 11:22 ` [Bug tree-optimization/59387] [4.9 Regression] " jakub at gcc dot gnu.org
2013-12-19 11:31 ` jakub at gcc dot gnu.org
2014-01-08 16:38 ` jakub at gcc dot gnu.org
2014-01-08 22:48 ` jakub at gcc dot gnu.org
2014-01-09 9:34 ` rguenth at gcc dot gnu.org
2014-01-10 14:56 ` jakub at gcc dot gnu.org
2014-01-13 19:14 ` jakub at gcc dot gnu.org
2014-01-15 21:43 ` law at redhat dot com
2014-01-16 19:15 ` jakub 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-59387-4-rdVAJJvr7U@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).