public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Sylvain Pion <Sylvain.Pion@sophia.inria.fr> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/3782: -fstats produces a segmentation fault Date: Tue, 10 Dec 2002 03:26:00 -0000 [thread overview] Message-ID: <20021210112603.27422.qmail@sources.redhat.com> (raw) The following reply was made to PR other/3782; it has been noted by GNATS. From: Sylvain Pion <Sylvain.Pion@sophia.inria.fr> To: ehrhardt@mathematik.uni-ulm.de, Sylvain.Pion@sophia.inria.fr, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: other/3782: -fstats produces a segmentation fault Date: Tue, 10 Dec 2002 12:16:31 +0100 On Mon, Dec 09, 2002 at 07:20:25PM -0000, ehrhardt@mathematik.uni-ulm.de wrote: > I can't reproduce this with recent gcc on a similar machine. > Does this still happen with your setup? Yes it does. With current mainline, I get : spion@mpino1212:~/GCC$ ./Linux/bin/gcc -v Reading specs from ./Linux/bin/../lib/gcc-lib/i686-pc-linux-gnu/3.3/specs Configured with: ../gcc/configure --prefix=/home/spion/GCC/Linux --enable-languages=c++ --with-as=/home/spion/BINUTILS/Linux-2.13/bin/as --with-ld=/home/spion/BINUTILS/Linux-2.13/bin/ld Thread model: posix gcc version 3.3 20021210 (experimental) spion@mpino1212:~/GCC$ ./Linux/bin/gcc -fstats -c foo.c cc1: warning: "-fstats" is valid for C++ but not for C/ObjC spion@mpino1212:~/GCC$ ./Linux/bin/g++ -fstats -c foo.C <internal>:0: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. -- Sylvain
next reply other threads:[~2002-12-10 11:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-10 3:26 Sylvain Pion [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-10 4:16 Christian Ehrhardt 2002-12-09 11:20 ehrhardt 2001-07-23 14:56 Sylvain.Pion
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=20021210112603.27422.qmail@sources.redhat.com \ --to=sylvain.pion@sophia.inria.fr \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).