public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/8047: loop with many exceptions causes segfault Date: Wed, 25 Sep 2002 15:46:00 -0000 [thread overview] Message-ID: <20020925224601.14017.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8047; it has been noted by GNATS. From: Andrew Pinski <pinskia@physics.uc.edu> To: Andreas Kloeckner <kloeckner@RTNA.DaimlerChrysler.COM> Cc: gcc-gnats@gcc.gnu.org, schroedl@RTNA.DaimlerChrysler.COM, king@RTNA.DaimlerChrysler.COM, wagner@RTNA.DaimlerChrysler.COM Subject: Re: c++/8047: loop with many exceptions causes segfault Date: Wed, 25 Sep 2002 15:44:17 -0700 That was a minute and half. Looks like a i686 vs i386 thing. Because if I run with -m386 it does the same thing as yours does. Look likes it still does it in the current cvs (3.3). here is my gcc -v output: Reading specs from /home/gates/pinskia/gcc311.linux/lib/gcc-lib/i686-pc-linux-gnu/3.1.1/ specs Configured with: /home/gates/pinskia/src/gnu/gcc/noncvs/gcc-3.1.1/configure --target=i686-pc-linux-gnu --prefix=/home/gates/pinskia/gcc311.linux --enable-threads=posix --enable-shared Thread model: posix gcc version 3.1.1 Thanks, Andrew Pinski On Wednesday, Sep 25, 2002, at 15:36 US/Pacific, Andreas Kloeckner wrote: > On Wed, Sep 25, 2002 at 03:28:19PM -0700, Andrew Pinski wrote: >> I do not see this problem on gcc 3.1.1 (self-compiled version) at all >> on i686 on redhat linux 7.3. >> 30597 pinskia 25 0 700 700 608 R 99.9 0.0 1:36 a.out >> >> Thanks, >> Andrew Pinski > > did you watch it for several seconds? for me, it grows at about > 100k/sec. > > Here's my gcc -v output: > > Reading specs from /usr/lib/gcc-lib/i386-linux/3.1.1/specs > Configured with: /mnt/data/gcc-3.1/gcc-3.1-3.1.1ds3/src/configure -v > --enable-languages=c,c++,java,f77,proto,objc,ada --prefix=/usr > --mandir=/usr/share/man --infodir=/usr/share/info > --with-gxx-include-dir=/usr/include/c++/3.1 --enable-shared > --with-system-zlib --enable-long-long --enable-nls > --without-included-gettext --enable-clocale=gnu --enable-__cxa_atexit > --enable-threads=posix --enable-java-gc=boehm --enable-objc-gc > i386-linux > Thread model: posix > gcc version 3.1.1 > > It's a Debian-compiled standard gcc-3.1 package. > > Andreas >
next reply other threads:[~2002-09-25 22:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-25 15:46 Andrew Pinski [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-04 8:21 lerdsuwa 2002-09-25 15:46 Andreas Kloeckner 2002-09-25 15:36 Andrew Pinski 2002-09-25 15:06 kloeckner
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=20020925224601.14017.qmail@sources.redhat.com \ --to=pinskia@physics.uc.edu \ --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).