From: Andrew Pinski <pinskia@physics.uc.edu>
To: mrs@apple.com (Mike Stump)
Cc: rearnsha@gcc.gnu.org (Richard Earnshaw),
dave.korn@artimi.com (Dave Korn),
ian@airs.com (Ian Lance Taylor),
gcc@gcc.gnu.org (gcc mailing list),
dewar@adacore.com (Robert Dewar),
pinskia@physics.uc.edu (Andrew Pinski)
Subject: Re: Why doesn't combine like volatiles? (volatile_ok again, sorry!)
Date: Mon, 28 Nov 2005 17:41:00 -0000 [thread overview]
Message-ID: <200511281741.jASHf9Bc001892@earth.phy.uc.edu> (raw)
In-Reply-To: <89A96DBE-1C78-4770-89D2-E44DEFB07A44@apple.com>
>
> On Nov 28, 2005, at 9:18 AM, Andrew Pinski wrote:
> > While it is true that GCC is not just an Ada compiler but I think
> > we should
> > follow a sane set of rules for GNU C which might mean following
> > Ada's rules
> > for this case.
>
> Because GNU C doesn't have rules carefully written to make this
> impossible, our rules are carefully written to make it possible. If
> you want to code in Ada, feel free.
Huh? they are not carefully written at all. This is why I said what
is GNU C? Again the language is not written out so it means anything.
If poeple want something defined the way they like it, please write some
documentation that way and post a patch. I could care which way it goes
except right now, we can do anything because it is not that well written
(well it is undocuemented).
-- Pinski
next prev parent reply other threads:[~2005-11-28 17:41 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 18:12 Dave Korn
2005-11-21 21:46 ` Ian Lance Taylor
2005-11-22 10:45 ` Richard Earnshaw
2005-11-22 15:33 ` Dave Korn
2005-11-22 15:52 ` Richard Earnshaw
2005-11-22 16:10 ` Robert Dewar
2005-11-27 3:18 ` Mike Stump
2005-11-27 3:14 ` Mike Stump
2005-11-28 11:01 ` Richard Earnshaw
2005-11-28 11:13 ` Robert Dewar
2005-11-28 13:09 ` Paolo Bonzini
2005-11-28 21:05 ` Laurent GUERBY
2005-11-28 22:26 ` Robert Dewar
2005-11-28 17:14 ` Mike Stump
2005-11-28 17:19 ` Andrew Pinski
2005-11-28 17:22 ` Mike Stump
2005-11-28 17:35 ` Mike Stump
2005-11-28 17:41 ` Andrew Pinski [this message]
2005-11-28 17:53 ` Mike Stump
2005-11-28 18:08 ` Joe Buck
2005-11-28 18:28 ` Mike Stump
2005-11-28 19:12 ` Robert Dewar
2005-11-28 19:56 ` Mike Stump
2005-11-28 20:01 ` Robert Dewar
2005-11-28 20:18 ` Gabriel Dos Reis
2005-11-28 20:21 ` Robert Dewar
2005-11-28 19:05 ` Robert Dewar
2005-11-28 19:53 ` Mike Stump
2005-11-28 17:11 ` Mike Stump
2005-11-28 17:29 ` Dave Korn
2005-11-28 18:14 ` Mike Stump
2005-11-23 19:54 ` Accidentally on the list Eric J. Goforth
2005-11-23 19:56 ` Gerald Pfeifer
2005-11-22 16:16 Why doesn't combine like volatiles? (volatile_ok again, sorry!) Richard Kenner
2005-11-22 18:38 ` Robert Dewar
2005-11-22 19:02 ` Dave Korn
2005-11-22 19:10 ` Robert Dewar
2005-11-22 20:39 ` Dave Korn
2005-11-23 11:27 ` Richard Earnshaw
2005-11-23 11:41 ` Robert Dewar
2005-11-23 12:04 ` Richard Earnshaw
2005-11-23 12:15 ` Robert Dewar
2005-11-28 17:28 Richard Kenner
2005-11-28 17:44 ` Mike Stump
2005-11-28 18:50 Richard Kenner
2005-11-28 20:25 ` Mike Stump
2005-11-28 20:40 ` Andrew Pinski
2005-11-28 21:55 ` Mike Stump
2005-11-28 22:14 ` Andrew Pinski
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=200511281741.jASHf9Bc001892@earth.phy.uc.edu \
--to=pinskia@physics.uc.edu \
--cc=dave.korn@artimi.com \
--cc=dewar@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=ian@airs.com \
--cc=mrs@apple.com \
--cc=rearnsha@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).