This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: c++/7884: code compiled with optimization flag causes segmentation violation
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: nobody at gcc dot gnu dot org
- Cc: gcc-prs at gcc dot gnu dot org,
- Date: 12 Sep 2002 12:36:01 -0000
- Subject: Re: c++/7884: code compiled with optimization flag causes segmentation violation
- Reply-to: Gabriel Dos Reis <gdr at integrable-solutions dot net>
The following reply was made to PR c++/7884; it has been noted by GNATS.
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: "Andreas Arnez" <ARNEZ@de.ibm.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/7884: code compiled with optimization flag causes segmentation violation
Date: 12 Sep 2002 14:22:23 +0200
"Andreas Arnez" <ARNEZ@de.ibm.com> writes:
| [1 <text/plain; us-ascii (7bit)>]
| > That particular extension doesn't play well with the rest of the
| > language and is causing more troubles than it solves any real
| > problems. It may disappear in some future releases of GCC.
|
| Then is there any way to instruct the compiler to yield a
| diagnostic for this?
None currently exists. But recent patches and discussions about that
extension (and its unexpected implications) may cause such a siwtch to
happen.
| I tried -ansi, -pedantic, and -Wall.
| I would have expected -ansi to consider casts as rvalues.
So would I.
-- Gaby