From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21574 invoked by alias); 12 Sep 2002 12:36:02 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 21557 invoked by uid 71); 12 Sep 2002 12:36:01 -0000 Date: Thu, 12 Sep 2002 05:36:00 -0000 Message-ID: <20020912123601.21556.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Gabriel Dos Reis Subject: Re: c++/7884: code compiled with optimization flag causes segmentation violation Reply-To: Gabriel Dos Reis X-SW-Source: 2002-09/txt/msg00206.txt.bz2 List-Id: The following reply was made to PR c++/7884; it has been noted by GNATS. From: Gabriel Dos Reis To: "Andreas Arnez" 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" writes: | [1 ] | > 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