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/55902] lto1 SIGSEGV
Date: Tue, 08 Jan 2013 09:49:00 -0000 [thread overview]
Message-ID: <bug-55902-4-PzFT3FW3cH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55902-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55902
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2013-01-08
Ever Confirmed|0 |1
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> 2013-01-08 09:48:55 UTC ---
I stronly suggest you try GCC 4.7.2 (that is, the latest available release)
when you run into LTO issues as well as recent binutils releases (what's
your binutils version? do you use gold?).
Does it only reproduce with -flto-partition=none? Can you try to reduce
the set of input source files by using partial linking (-r -nostdlib)?
Usually this reduces the set of input sources to two.
The google doc is not accessible for me.
next prev parent reply other threads:[~2013-01-08 9:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 19:50 [Bug lto/55902] New: " vhaisman at gmail dot com
2013-01-07 19:54 ` [Bug lto/55902] " vhaisman at gmail dot com
2013-01-07 20:19 ` vhaisman at gmail dot com
2013-01-08 9:49 ` rguenth at gcc dot gnu.org [this message]
2013-01-08 15:00 ` vhaisman at gmail dot com
2013-01-08 18:27 ` vhaisman at gmail dot com
2013-11-25 21:24 ` ktietz at gcc dot gnu.org
2022-01-09 4:35 ` pinskia 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-55902-4-PzFT3FW3cH@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).