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: Thu, 01 Jul 2010 10:47:00 -0000 [thread overview]
Message-ID: <20100701104702.10399.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44724-19380@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from moonshine at kapsi dot fi 2010-07-01 10:47 -------
Created an attachment (id=21055)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21055&action=view)
Preprocessed source files to reproduce this problem
I was able to reduce this to two (2) source files. Quite an improvement,
original was more than hundred files :) The exact command I used to reproduce
this bug is:
g++ -r -nostdlib -O3 -fomit-frame-pointer -funroll-loops -march=pentium4 -flto
-fuse-linker-plugin sid.ii wave.ii
The .ii files were created with
g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\"
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"resid\"
-DVERSION=\"0.16vice\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1
-DSIZEOF_INT=4 -I. -I. -O3 -fomit-frame-pointer -funroll-loops
-march=pentium4 -flto -fuse-linker-plugin -MT sid.o -MD -MP -MF ".deps/sid.Tpo"
-E sid.cc > sid.ii
g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\"
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"resid\"
-DVERSION=\"0.16vice\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1
-DSIZEOF_INT=4 -I. -I. -O3 -fomit-frame-pointer -funroll-loops
-march=pentium4 -flto -fuse-linker-plugin -MT wave.o -MD -MP -MF
".deps/wave.Tpo" -E wave.cc > wave.ii
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44724
next prev parent reply other threads:[~2010-07-01 10:47 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 ` [Bug lto/44724] " moonshine at kapsi dot fi
2010-06-30 13:00 ` rguenth at gcc dot gnu dot org
2010-07-01 10:47 ` moonshine at kapsi dot fi [this message]
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=20100701104702.10399.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).