public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sandra at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64377] nios2 compile error in options-save.c
Date: Tue, 13 Jan 2015 20:17:00 -0000	[thread overview]
Message-ID: <bug-64377-4-cfRM6rOuaF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64377-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64377

--- Comment #13 from Sandra Loosemore <sandra at codesourcery dot com> ---
I think the new version of the patch in comment 11 is probably OK.  I ran the
entire gcc testsuite (but not g++, etc yet) and have a couple hundred
regressions compared to my r217010 build, but I don't see a pattern of them
being obviously lto-related.  (I started skimming over them and they look
mostly like broken test cases.)


  parent reply	other threads:[~2015-01-13 20:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-22 15:23 [Bug target/64377] New: " joel at gcc dot gnu.org
2014-12-22 15:27 ` [Bug target/64377] " joel at gcc dot gnu.org
2014-12-29  2:11 ` sandra at codesourcery dot com
2015-01-08 22:25 ` sandra at codesourcery dot com
2015-01-12 18:02 ` joel at gcc dot gnu.org
2015-01-13 14:01 ` sandra at codesourcery dot com
2015-01-13 15:27 ` marxin at gcc dot gnu.org
2015-01-13 20:17 ` sandra at codesourcery dot com [this message]
2015-01-13 20:40 ` marxin at gcc dot gnu.org
2015-01-13 23:14 ` sandra at codesourcery dot com
2015-01-14 11:22 ` marxin at gcc dot gnu.org
2015-01-15  9:54 ` marxin at gcc dot gnu.org
2015-01-20 18:46 ` joel at gcc dot gnu.org
2015-01-20 19:00 ` joel at gcc dot gnu.org
2015-02-09 16:17 ` marxin at gcc dot gnu.org
2015-02-09 16:22 ` joel 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-64377-4-cfRM6rOuaF@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).