public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/60319] wrong code (that hangs) by LTO at -Os and above on x86_64-linux-gnu
Date: Tue, 25 Feb 2014 08:58:00 -0000	[thread overview]
Message-ID: <bug-60319-4-N12f9TuOFq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60319-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Tue Feb 25 08:57:42 2014
New Revision: 208112

URL: http://gcc.gnu.org/viewcvs?rev=208112&root=gcc&view=rev
Log:
2014-02-25  Richard Biener  <rguenther@suse.de>

    PR lto/60319
    * lto-opts.c (lto_write_options): Output non-explicit conservative
    -fwrapv, -fno-trapv and -fno-strict-overflow.
    * lto-wrapper.c (merge_and_complain): Handle merging those options.
    (run_gcc): And pass them through.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/lto-opts.c
    trunk/gcc/lto-wrapper.c


  parent reply	other threads:[~2014-02-25  8:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-60319-4@http.gcc.gnu.org/bugzilla/>
2014-02-24  8:37 ` rguenth at gcc dot gnu.org
2014-02-24  8:42 ` rguenth at gcc dot gnu.org
2014-02-24  9:00 ` su at cs dot ucdavis.edu
2014-02-24  9:20 ` rguenth at gcc dot gnu.org
2014-02-24 15:40 ` su at cs dot ucdavis.edu
2014-02-24 16:36 ` rguenth at gcc dot gnu.org
2014-02-24 17:01 ` rguenth at gcc dot gnu.org
2014-02-25  8:58 ` rguenth at gcc dot gnu.org [this message]
2014-02-25  9:00 ` rguenth 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-60319-4-N12f9TuOFq@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).