public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/63333] lto, 1to1 segmentation fault
Date: Thu, 25 Sep 2014 07:54:00 -0000 [thread overview]
Message-ID: <bug-63333-4-DqteuI6J6G@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63333-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63333
--- Comment #4 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 25 Sep 2014, avi@cloudius-systems.com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63333
>
> --- Comment #2 from Avi Kivity <avi@cloudius-systems.com> ---
> I managed to narrow it down to 400 lines (before preprocessing), strangely in
> one file. Now, practically anything I touch turns the segfault into link
> errors.
>
> Is this useful? I could share it privately.
It's already useful.
next prev parent reply other threads:[~2014-09-25 7:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 15:40 [Bug lto/63333] New: " avi@cloudius-systems.com
2014-09-23 10:37 ` [Bug lto/63333] " rguenth at gcc dot gnu.org
2014-09-25 4:03 ` avi@cloudius-systems.com
2014-09-25 6:15 ` trippels at gcc dot gnu.org
2014-09-25 7:54 ` rguenther at suse dot de [this message]
2014-09-26 11:36 ` avi@cloudius-systems.com
2014-09-26 11:49 ` rguenther at suse dot de
2015-02-24 14:06 ` avi@cloudius-systems.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-63333-4-DqteuI6J6G@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).