This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/41230] [LTO] Segfault using -flto with -fvar-tracking-assignments
- From: "rmansfield at qnx dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 2 Sep 2009 22:50:18 -0000
- Subject: [Bug lto/41230] [LTO] Segfault using -flto with -fvar-tracking-assignments
- References: <bug-41230-11406@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #6 from rmansfield at qnx dot com 2009-09-02 22:50 -------
(In reply to comment #5)
> Note that in general you have to repeat all options on the link command line,
> otherwise you are building with -O0 there.
Yep, I realize that. I just came across this crash by accidentally leaving
-fvar-tracking-assignments off the link line. Improper usage that cause
crashes/ICEs are still worth PRs, right?
The non-reduced testcase was built with -O2 as well as a number of other
options for compiling/linking but since they didn't effect whether or not the
crash occurred I left them out of the report.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41230