public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mikestump@comcast.net>
To: Mark Mitchell <mark@codesourcery.com>
Cc: Nathan Sidwell <nathan@codesourcery.com>,
	Michael Matz <matz@suse.de>,
	Richard Guenther <richard.guenther@gmail.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [gimple] assignments to volatile
Date: Thu, 24 Jun 2010 15:53:00 -0000	[thread overview]
Message-ID: <4936DDA8-4C55-4CF8-8CA7-D8B4435863BF@comcast.net> (raw)
In-Reply-To: <4C22F307.6010403@codesourcery.com>

On Jun 23, 2010, at 10:54 PM, Mark Mitchell wrote:
> Mike Stump wrote:
>> If someone wanted to fix gcc, the proper way would be to get the C
>> and C++ committees on the same page, nail it down, or make it a hard
>> error, and remove any latitude and confusion and make them agree.
> 
> Are you saying that C and C++ require different behavior for:
> 
>  x = y = z;
> 
> where "y" is volatile?

In my book no, they do not.  I think a reasonable person can also say that they do, because the C standard can be read in a way that is difference from the C standard.  C++ requires a re-read of y.  For consistency, the C standard should be read in a way that requires the re-read of y.

> Or are you saying that C++ requires that "y" be read while C does not specify it one way or the other?

This is the essence of the second point above.

> Please state your position more clearly.

C++ requires a re-read of y, the patch was going to remove the re-read, I objected because the patch then makes the compiler not conform to the C++ standard.  The patch was going to make C differ from C++, should the semantic for C++ be put back to match the standard. I really don't like to see the behavior of C++ and C differ when they don't need to.

>> An assignment expression has the value of the left operand after the 
>> assignment
> 
> I don't think this is nearly as clear as you do.

Ok.  Let's talk about it.  I objected because people seems to be going in the wrong direction.  Maybe I just misunderstood the effect of the patch.  The patch removes the re-read of y, right?

> Furthermore, I think existing practice from other embedded compilers is pretty important;

But to the exclusion of all of gcc users and the c++ standard?

> However, I cannot see any good justification for:
> 
>  int x;
>  volatile int y;
>  int z;
>  x ? y = z : 0
> 
> generating a read from "y" while:
> 
>  x ? y = 0 : 0
> 
> does not.

I wasn't arguing this case.  I believe both standards have them behaving the same.

  reply	other threads:[~2010-06-24 14:24 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21 12:44 Nathan Sidwell
2010-06-21 13:26 ` Richard Guenther
2010-06-21 13:55   ` Michael Matz
2010-06-21 14:07     ` Richard Guenther
2010-06-21 14:09     ` Nathan Sidwell
2010-06-21 14:17       ` Michael Matz
2010-06-21 14:19         ` Richard Guenther
2010-06-21 14:53           ` Michael Matz
2010-06-21 14:17     ` IainS
2010-06-21 14:24       ` Michael Matz
2010-06-21 14:50         ` Nathan Sidwell
2010-06-21 15:24           ` Michael Matz
2010-06-22 11:36             ` Dave Korn
2010-06-23 20:16             ` Mike Stump
2010-06-24 11:51               ` Michael Matz
2010-06-21 15:24         ` Nathan Sidwell
2010-06-21 15:46           ` Michael Matz
2010-06-22 15:37     ` Mark Mitchell
2010-06-22 15:37       ` Jakub Jelinek
2010-06-22 15:57         ` Paul Koning
2010-06-22 15:47       ` Michael Matz
2010-06-22 15:58         ` Mark Mitchell
2010-06-23 11:38           ` Nathan Sidwell
2010-06-23 14:05             ` Mark Mitchell
2010-06-23 14:06               ` Michael Matz
2010-06-23 16:00                 ` Richard Guenther
2010-06-23 16:25               ` Paul Koning
2010-06-23 17:13                 ` Mark Mitchell
2010-06-23 19:16               ` Mike Stump
2010-06-24 10:22                 ` Mark Mitchell
2010-06-24 15:53                   ` Mike Stump [this message]
2010-06-24 16:00                     ` Mark Mitchell
2010-06-24 19:37                       ` Mike Stump
2010-06-25  9:37                         ` Nathan Sidwell
2010-06-25 19:06                           ` Mike Stump
2010-06-25 21:33                             ` Mark Mitchell
2010-06-26  9:35                               ` Mike Stump
2010-06-26 10:18                                 ` Mark Mitchell
2010-06-26 12:18                                   ` Richard Guenther
2010-06-26 19:52                                     ` Michael Matz
2010-06-26 19:57                                       ` Mark Mitchell
2010-06-26 20:08                                         ` Michael Matz
2010-06-26 22:13                                           ` Mark Mitchell
2010-06-28  9:20                                             ` Nathan Sidwell
2010-06-28  9:27                                               ` Nathan Sidwell
2010-06-26 10:20                                 ` Richard Kenner
2010-06-28  9:52                             ` Nathan Sidwell
2010-06-30 22:52                               ` Mike Stump
2010-07-05  8:59                                 ` Nathan Sidwell
2010-07-09  5:27                                   ` Mike Stump
2010-07-09  7:22                                     ` Nathan Sidwell
2010-07-16  8:10                                       ` Nathan Sidwell
2010-07-16 15:20                                         ` Mark Mitchell
2010-07-19  8:41                                           ` Nathan Sidwell
2010-08-13  9:56                                           ` Nathan Sidwell
2010-08-18 15:32                                             ` Mark Mitchell
2010-08-18 16:18                                               ` Richard Guenther
2010-08-18 18:04                                                 ` Mike Stump
2010-08-19 11:11                                               ` Nathan Sidwell
2010-08-20  4:22                                                 ` Mark Mitchell
2010-08-20 16:59                                                   ` Mike Stump
2010-08-20 18:00                                             ` H.J. Lu
2010-08-20 18:33                                               ` Nathan Sidwell
2010-06-25  9:20                       ` Nathan Sidwell
2010-06-24 10:23                 ` Nathan Sidwell
2010-06-24 17:05                   ` Mike Stump
2010-06-24 17:29                     ` Paul Koning
2010-06-25  9:26                     ` Nathan Sidwell
2010-06-25 18:20                       ` Mike Stump
2010-06-28  8:49                         ` Nathan Sidwell
2010-07-01  1:02                           ` Mike Stump
2010-07-05  9:02                             ` Nathan Sidwell
2010-07-09  5:14                               ` Mike Stump
2010-07-09  7:20                                 ` Nathan Sidwell
2010-06-22 15:56       ` Paul Koning
2010-06-22 12:08   ` Nathan Sidwell
2010-06-22 12:25     ` Richard Guenther
2010-06-22 13:12     ` Michael Matz
2010-06-22 13:54       ` Nathan Sidwell
2010-06-22 15:21         ` Michael Matz
2010-06-22 16:12           ` Joseph S. Myers

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=4936DDA8-4C55-4CF8-8CA7-D8B4435863BF@comcast.net \
    --to=mikestump@comcast.net \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    --cc=matz@suse.de \
    --cc=nathan@codesourcery.com \
    --cc=richard.guenther@gmail.com \
    /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).