From: Richard Guenther <richard.guenther@gmail.com>
To: Adrian von Bidder <avbidder@fortytwo.ch>
Cc: gcc@gcc.gnu.org
Subject: Re: How to report an ICE in -flto?
Date: Fri, 23 Apr 2010 13:05:00 -0000 [thread overview]
Message-ID: <p2m84fc9c001004230511k3edc59aaz6664c4c1fc7131ac@mail.gmail.com> (raw)
In-Reply-To: <201004231324.18012@fortytwo.ch>
On Fri, Apr 23, 2010 at 1:22 PM, Adrian von Bidder <avbidder@fortytwo.ch> wrote:
> Heyho!
>
> Usually I'd report an ICE by using -save-temps and reporting with the full
> commandline.
>
> Now an ICE with -flto happens during the link stage. And, since KDE is
> quite a bit of code, there's a ton of object files and shared libraries
> specified on the commandline.
>
> Is there a way to cut this down to a sane level?
There is a little bit of information on
http://gcc.gnu.org/wiki/A_guide_to_testcase_reduction
Richard.
> cheers
> -- vbi
>
> --
> Today is Pungenday, the 40th day of Discord in the YOLD 3176
>
prev parent reply other threads:[~2010-04-23 12:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 12:00 Adrian von Bidder
2010-04-23 13:05 ` Richard Guenther [this message]
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=p2m84fc9c001004230511k3edc59aaz6664c4c1fc7131ac@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=avbidder@fortytwo.ch \
--cc=gcc@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).