public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc-bugzilla at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/18363] New: build fails when using optimization Date: Sun, 07 Nov 2004 21:05:00 -0000 [thread overview] Message-ID: <20041107210501.18363.Alex.Prinsier@aphexer.homedns.org> (raw) The same code builds without the -O flag but gcc 'crashes' when adding optimization... I wasn't sure if I had to include the binary Config.ii.bz2 in this mail... I'm using gccbug so it seems a bit odd to include binary data here. Instead I uploaded it, you can download it here: http://aphexer.dyndns.org/bug/Config.ii.bz2 (in the same directory there are some other maybe interesting files). Environment: System: Linux slack 2.4.26 #21 Mon Jun 14 19:17:44 PDT 2004 i686 unknown unknown GNU/Linux Architecture: i686 host: i486-slackware-linux-gnu build: i486-slackware-linux-gnu target: i486-slackware-linux-gnu configured with: ../gcc-3.3.4/configure --prefix=/usr --enable-shared --enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose --target=i486-slackware-linux --host=i486-slackware-linux How-To-Repeat: I use this to compile: g++ -Wall -save-temps -DHAVE_CONFIG_H -I. -I. -I../.. -g -O -MT Config.o -MD -MP -MF ".deps/Config.Tpo" -c -o Config.o Config.cpp ------- Additional Comments From Alex dot Prinsier at aphexer dot homedns dot org 2004-11-07 21:05 ------- Fix: Remove the -O argument. -- Summary: build fails when using optimization Product: gcc Version: 3.3.4 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Alex dot Prinsier at aphexer dot homedns dot org CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i486-slackware-linux-gnu GCC host triplet: i486-slackware-linux-gnu GCC target triplet: i486-slackware-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18363
next reply other threads:[~2004-11-07 21:05 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-11-07 21:05 gcc-bugzilla at gcc dot gnu dot org [this message] 2004-11-07 21:08 ` [Bug c++/18363] " aphexer at mailhaven dot com 2004-11-07 21:10 ` aphexer at mailhaven dot com 2004-11-07 21:13 ` pinskia at gcc dot gnu dot org 2004-11-07 21:13 ` [Bug rtl-optimization/18363] " pinskia at gcc dot gnu dot org 2004-11-07 21:15 ` aphexer at mailhaven dot com 2004-11-07 21:16 ` pinskia at gcc dot gnu dot org 2004-11-07 21:22 ` aphexer at mailhaven dot com 2004-11-07 21:24 ` pinskia at gcc dot gnu dot org 2004-11-07 21:28 ` aphexer at mailhaven dot com 2004-11-07 21:29 ` pinskia at gcc dot gnu dot org
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=20041107210501.18363.Alex.Prinsier@aphexer.homedns.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: linkBe 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).