public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus at trippelsdorf dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/54795] [4.8 Regression] Random profiledbootstrap failure with LTO
Date: Wed, 21 Nov 2012 21:53:00 -0000	[thread overview]
Message-ID: <bug-54795-4-RwOj7scmbv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54795-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #14 from Markus Trippelsdorf <markus at trippelsdorf dot de> 2012-11-21 21:52:26 UTC ---
LTO gets miscompiled.

If I configure with:
~/gcc/configure --disable-bootstrap --disable-werror --disable-multilib
--enable-languages=c,c++ --enable-checking=yes,valgrind
and build with gcc-4.7, then the bad memory access in LTO vanishes.

This could be a dup of Bug 55430 (LRA miscompilation issue).


  parent reply	other threads:[~2012-11-21 21:53 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03 14:32 [Bug bootstrap/54795] New: " hjl.tools at gmail dot com
2012-10-04 12:13 ` [Bug bootstrap/54795] " rguenth at gcc dot gnu.org
2012-10-11 17:41 ` ubizjak at gmail dot com
2012-10-11 17:54 ` hjl.tools at gmail dot com
2012-10-11 17:55 ` markus at trippelsdorf dot de
2012-11-16  0:34 ` hjl.tools at gmail dot com
2012-11-16 19:36 ` markus at trippelsdorf dot de
2012-11-17 15:48 ` hjl.tools at gmail dot com
2012-11-17 16:16 ` hjl.tools at gmail dot com
2012-11-17 16:30 ` hjl.tools at gmail dot com
2012-11-17 16:48 ` hjl.tools at gmail dot com
2012-11-17 17:20 ` hjl.tools at gmail dot com
2012-11-17 17:30 ` hjl.tools at gmail dot com
2012-11-18 13:16 ` hjl.tools at gmail dot com
2012-11-19 21:04 ` hjl.tools at gmail dot com
2012-11-21 21:53 ` markus at trippelsdorf dot de [this message]
2012-11-23 20:33 ` hjl.tools at gmail dot com
2012-11-24  9:18 ` markus at trippelsdorf dot de
2012-11-24 16:39 ` hjl.tools at gmail dot com
2012-11-24 16:49 ` hjl.tools at gmail dot com
2012-11-24 17:03 ` hjl.tools at gmail dot com
2012-11-24 19:48 ` [Bug bootstrap/54795] [4.8 Regression] LTO miscompiled external array access markus at trippelsdorf dot de
2012-11-25  7:34 ` hjl.tools at gmail dot com
2012-11-25 17:55 ` [Bug lto/54795] " hjl.tools at gmail dot com
2012-11-25 22:38 ` hjl.tools at gmail dot com
2012-11-25 22:40 ` hjl.tools at gmail dot com
2012-11-26 12:24 ` rguenth at gcc dot gnu.org
2012-11-26 13:29 ` hjl.tools at gmail dot com
2012-11-27 13:57 ` hjl at gcc dot gnu.org
2012-11-28 14:39 ` [Bug lto/54795] global-buffer-overflow in lto_write_options hjl at gcc dot gnu.org
2012-11-28 14:40 ` hjl.tools at gmail dot com

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-54795-4-RwOj7scmbv@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).