Re: c++/8067: g++ 3.2 internal error: Segmentation fault

[Gabriel Dos Reis <gdr@integrable-solutions.net>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]

The following reply was made to PR c++/8067; it has been noted by GNATS.

From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Pop Sébastian <pop@gauvain.u-strasbg.fr>
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: 06 Oct 2002 21:10:01 +0200

 Pop Sébastian <pop@gauvain.u-strasbg.fr> writes:
 
 | Hi Jason,
 | 
 | On Tue, Oct 01, 2002 at 10:44:24AM +0100, Jason Merrill wrote:
 | > Thanks, but your patch is just a workaround; the problem is that we think
 | > we're dealing with a variable declared in the for-init-stmt, but we really
 | > aren't.  
 | Ok, so we have to teach G++ that __PRETTY_FUNCTION__ is not a local declaration 
 | in the FOR_INIT.
 
 More specifically, we have to teach the front-end about gracious
 handling of similar erroneous constructs in the for-init-statement.
 
 | 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.
 
 -- Gaby