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: Mon, 24 Feb 2014 08:42:00 -0000 [thread overview] Message-ID: <bug-60319-4-FD2rrKVsmQ@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 #2 from Richard Biener <rguenth at gcc dot gnu.org> --- 4.7 and lower is expected to show this behavior due to the bug that c++ is not properly implemented as c = (char)((int)c + 1) and thus we think that overflow is undefined. 4.8 and above has that fixed and thus shows different, working behavior.
next prev parent reply other threads:[~2014-02-24 8:42 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 [this message] 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 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-FD2rrKVsmQ@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: linkBe 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).