public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/7884: code compiled with optimization flag causes segmentation violation
Date: Thu, 12 Sep 2002 05:36:00 -0000 [thread overview]
Message-ID: <20020912123601.21556.qmail@sources.redhat.com> (raw)
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
next reply other threads:[~2002-09-12 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 5:36 Gabriel Dos Reis [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-12 4:16 Gabriel Dos Reis
2002-09-12 1:46 arnez
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=20020912123601.21556.qmail@sources.redhat.com \
--to=gdr@integrable-solutions.net \
--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: link
Be 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).