public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/58640] [4.9 Regression] wrong code (segfaults) at -O3 on x86_64-linux-gnu
Date: Sun, 08 Dec 2013 17:05:00 -0000	[thread overview]
Message-ID: <bug-58640-4-a1qD6kv1IW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58640-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #13 from Oleg Endo <olegendo at gcc dot gnu.org> ---
(In reply to Jeffrey A. Law from comment #12)
> Oleg, I just worked through an independent problem that I saw locally that
> probably explains your SH issue as well.  I expect to have a fix in the
> trunk shortly.  I'll let you know so you can test it.

Jeff, do you have any updates regarding this?  The issue is still there on
current trunk rev.


  parent reply	other threads:[~2013-12-08 17:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-06  5:23 [Bug tree-optimization/58640] New: " su at cs dot ucdavis.edu
2013-10-06 12:31 ` [Bug tree-optimization/58640] " mikpelinux at gmail dot com
2013-10-10 11:59 ` [Bug tree-optimization/58640] [4.9 Regression] " rguenth at gcc dot gnu.org
2013-10-10 19:23 ` law at redhat dot com
2013-10-10 20:09 ` law at redhat dot com
2013-10-10 20:47 ` law at redhat dot com
2013-10-11  3:07 ` law at redhat dot com
2013-10-11 20:31 ` law at gcc dot gnu.org
2013-10-11 20:32 ` law at redhat dot com
2013-10-12  0:56 ` su at cs dot ucdavis.edu
2013-10-14  9:15 ` rguenth at gcc dot gnu.org
2013-10-14  9:17 ` rguenth at gcc dot gnu.org
2013-11-09  6:02 ` law at redhat dot com
2013-12-08 17:05 ` olegendo at gcc dot gnu.org [this message]
2013-12-10  6:55 ` law at redhat dot com
2013-12-10 11:20 ` olegendo 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-58640-4-a1qD6kv1IW@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).