public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "martin at mpa-garching dot mpg dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/19266] New: [mudflap] ICE when compiling with -fmudflap -O Date: Wed, 05 Jan 2005 15:43:00 -0000 [thread overview] Message-ID: <20050105154223.19266.martin@mpa-garching.mpg.de> (raw) Current g++ produces an ICE when trying to compile the attached test case. Sorry, I had no time today to try a reduction, so it is very large. I'll try to find a shorter testcase as soon as I have more time. BTW, which component should I use for bug reports concerning mudflap itself (not libmudflap)? ~/data/planck/LevelS>g++ -v -c -O -fmudflap testcase.ii Using built-in specs. Configured with: /scratch/gcc/configure --quiet --prefix=/afs/mpa/data/martin/ugcc --enable-languages=c++,f95 --with-gmp=/afs/mpa/data/martin/mygmp Thread model: posix gcc version 4.0.0 20050105 (experimental) /afs/mpa/data/martin/ugcc/libexec/gcc/i686-pc-linux-gnu/4.0.0/cc1plus -fpreprocessed testcase.ii -quiet -dumpbase testcase.ii -mtune=pentiumpro -auxbase testcase -O -version -fmudflap -fno-builtin -fno-merge-constants -o /tmp/ccrlkYrZ.s GNU C++ version 4.0.0 20050105 (experimental) (i686-pc-linux-gnu) compiled by GNU C version 4.0.0 20050105 (experimental). GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096 cxxsupport/fitshandle.cc: In member function 'void fitshandle::init_bintab()': cxxsupport/fitshandle.cc:99: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. -- Summary: [mudflap] ICE when compiling with -fmudflap -O Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: other AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: martin at mpa-garching dot mpg dot de CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19266
next reply other threads:[~2005-01-05 15:43 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-05 15:43 martin at mpa-garching dot mpg dot de [this message] 2005-01-05 15:44 ` [Bug other/19266] " martin at mpa-garching dot mpg dot de 2005-01-05 15:46 ` martin at mpa-garching dot mpg dot de 2005-01-05 15:51 ` pinskia at gcc dot gnu dot org 2005-01-05 15:51 ` pinskia at gcc dot gnu dot org 2005-01-05 19:41 ` pinskia at gcc dot gnu dot org 2005-01-05 19:45 ` martin at mpa-garching dot mpg dot de 2005-01-05 20:36 ` pinskia at gcc dot gnu dot org 2005-01-06 2:50 ` fche at redhat dot com 2005-04-08 13:51 ` pinskia at gcc dot gnu dot org 2005-04-12 16:50 ` fche at redhat dot com 2005-04-12 18:09 ` cvs-commit at gcc dot gnu dot org 2005-04-12 18:10 ` fche at redhat dot com 2005-06-15 3:29 ` pinskia at gcc dot gnu dot org 2005-06-23 11:35 ` reichelt at gcc dot gnu dot org 2005-08-15 14:12 ` pinskia at gcc dot gnu dot org 2005-08-24 11:54 ` 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=20050105154223.19266.martin@mpa-garching.mpg.de \ --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).