public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Berger David-MGI2063 <dberger@motorola.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: optimization/10423: -fvolatile switch not working in gcc 3.2- 3 when using -O2
Date: Wed, 16 Apr 2003 18:16:00 -0000	[thread overview]
Message-ID: <20030416181600.26115.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/10423; it has been noted by GNATS.

From: Berger David-MGI2063 <dberger@motorola.com>
To: "'Zack Weinberg'" <zack@codesourcery.com>
Cc: "'gcc-gnats@gcc.gnu.org'" <gcc-gnats@gcc.gnu.org>,
   "'gcc-bugs@gcc.gnu.org'" <gcc-bugs@gcc.gnu.org>
Subject: RE: optimization/10423: -fvolatile switch not working in gcc 3.2-
	3 when using -O2
Date: Wed, 16 Apr 2003 11:06:25 -0700

 Why are they being removed ?!?  Are you just going to break all the legacy programs out there? 
 
 -----Original Message-----
 From: Zack Weinberg [mailto:zack@codesourcery.com] 
 Sent: Wednesday, April 16, 2003 11:03 AM
 To: David Berger
 Cc: gcc-gnats@gcc.gnu.org; gcc-bugs@gcc.gnu.org
 Subject: Re: optimization/10423: -fvolatile switch not working in gcc 3.2-3 when using -O2
 
 
 dberger@motorola.com writes:
 
 > Compile with following using "gcc -O2 -fvolatile -S":
 >
 > void test(void)
 > {
 >   *(char *)0x100 = 1;
 >   *(char *)0x100 = 1;
 >   *(char *)0x100 = 1;
 >   *(char *)0x100 = 1;
 > }
 
 Allow me to refer you to the release notes for gcc 3.4 (that will be):
 
   GCC no longer accepts the options -fvolatile, -fvolatile-global and
   -fvolatile-static. It is unlikely that they worked correctly in any
   3.x release.
 
 Note in particular the last sentence.  You've just confirmed that it doesn't work.
 
 (to the list:) How about we remove these options from 3.2.3 and 3.3 as well?  It does not help anyone for them to be present but nonfunctional.
 
 zw


                 reply	other threads:[~2003-04-16 18:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030416181600.26115.qmail@sources.redhat.com \
    --to=dberger@motorola.com \
    --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).