public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "moonshine at kapsi dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/44724] LTO segfault
Date: Wed, 30 Jun 2010 12:28:00 -0000 [thread overview]
Message-ID: <20100630122752.23493.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44724-19380@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from moonshine at kapsi dot fi 2010-06-30 12:27 -------
(In reply to comment #0)
I forgot to add that I configured VICE with a following command:
CFLAGS='-flto -fuse-linker-plugin -O3 -fomit-frame-pointer -march=pentium4'
CXXFLAGS='-O3 -fomit-frame-pointer -funroll-loops -march=pentium4 -flto
-fuse-linker-plugin' ./configure --prefix=/home/misty/gcc --enable-gnomeui
--enable-fullscreen; make
If you forget --enable-gnomeui, build will fail in my experience, so this is
important.
--
moonshine at kapsi dot fi changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|LTO segfault |LTO segfault
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44724
next prev parent reply other threads:[~2010-06-30 12:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 12:23 [Bug lto/44724] New: " moonshine at kapsi dot fi
2010-06-30 12:28 ` moonshine at kapsi dot fi [this message]
2010-06-30 13:00 ` [Bug lto/44724] " rguenth at gcc dot gnu dot org
2010-07-01 10:47 ` moonshine at kapsi dot fi
2010-07-01 11:18 ` moonshine at kapsi dot fi
2010-07-01 11:35 ` [Bug lto/44724] LTO segfault with -fuse-linker-plugin rguenth at gcc dot gnu dot org
2010-07-01 11:41 ` rguenth at gcc dot gnu dot org
2010-07-06 12:57 ` moonshine at kapsi dot fi
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=20100630122752.23493.qmail@sourceware.org \
--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).