public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Giovanni Bajo" <giovannibajo@libero.it> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/10373: Attempt to compile STLport causes segmentation fault Date: Fri, 11 Apr 2003 02:46:00 -0000 [thread overview] Message-ID: <20030411024600.26175.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/10373; it has been noted by GNATS. From: "Giovanni Bajo" <giovannibajo@libero.it> To: <gcc-gnats@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, <nobody@gcc.gnu.org>, <jkolodzi@uiuc.edu>, <gcc-prs@gcc.gnu.org> Cc: Subject: Re: c++/10373: Attempt to compile STLport causes segmentation fault Date: Fri, 11 Apr 2003 04:44:38 +0200 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p r=10373 Redux: ------------------------------------------- namespace A {} namespace B {} namespace A { using namespace B; } namespace B { using namespace A; } void Foo(void) { using namespace A; } ------------------------------------------- pr10373.cpp: In function `void Foo()': pr10373.cpp:12: internal error: Segmentation fault Confirmed on 3.2 and 3.2.2. Worked on 2.95, and works on 3.3 20030401. So, it's a regression on the 3.2 branch only, and I'm not sure there is more time for patches for 3.2. If this works on 3.4 as well, the PR should be closed as 'fixed'. For the poster: the obvious workaround is to modify the function where the ICE happens so that it does not use an internal "using namespace std;". Just qualify everything needed with "std::", and the code should compile. You're welcome to submit such a patch to the STLPort guys as a workaround for GCC 3.2. Giovanni Bajo
next reply other threads:[~2003-04-11 2:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-11 2:46 Giovanni Bajo [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-11 14:17 bangerth 2003-04-11 2:26 jkolodzi
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=20030411024600.26175.qmail@sources.redhat.com \ --to=giovannibajo@libero.it \ --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).