public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Pop Sébastian" <pop@gauvain.u-strasbg.fr> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/8067: g++ 3.2 internal error: Segmentation fault Date: Mon, 07 Oct 2002 14:26:00 -0000 [thread overview] Message-ID: <20021007212601.25119.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8067; it has been noted by GNATS. From: =?iso-8859-1?Q?Pop_S=E9bastian?= <pop@gauvain.u-strasbg.fr> To: Gabriel Dos Reis <gdr@integrable-solutions.net> Cc: Jason Merrill <jason@redhat.com>, Reichelt <reichelt@igpm.rwth-aachen.de>, gcc-gnats@gcc.gnu.org, y_fedor@ciam.ru, gcc-patches@gcc.gnu.org Subject: Re: c++/8067: g++ 3.2 internal error: Segmentation fault Date: Mon, 7 Oct 2002 23:14:02 +0200 > > | What about the following patch for solving the PR following the first suggestion? > > Does it handle similar constructs where you replace > __PRETTY_FUNCTION__ with another id-expression? I'm under the > impression that it does not. > I tested the patch with "make check-c++" and results are exactly the same as on the original version. === g++ Summary === # of expected passes 6979 # of unexpected failures 598 # of unexpected successes 1 # of expected failures 91 # of untested testcases 9 # of unsupported tests 3 /home/pop/gcc/main/bin/gcc/testsuite/../g++ version gcc 3.3 20021005 (experimental) === libstdc++-v3 Summary === # of expected passes 397 # of unexpected failures 16 # of unexpected successes 1 # of expected failures 26 Sebastian
next reply other threads:[~2002-10-07 21:26 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-07 14:26 Pop Sébastian [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-23 17:14 mmitchel 2002-10-23 15:06 mmitchel 2002-10-06 12:16 Gabriel Dos Reis 2002-10-06 12:06 Pop Sébastian 2002-10-04 11:46 Jason Merrill 2002-09-30 13:06 Pop Sébastian 2002-09-30 10:36 Pop Sébastian 2002-09-30 9:56 Reichelt 2002-09-28 6:32 lerdsuwa 2002-09-27 0:06 y_fedor
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=20021007212601.25119.qmail@sources.redhat.com \ --to=pop@gauvain.u-strasbg.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).