This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: pointer post-incr problem with GCC 3.3.3 ??

From: Falk Hueffner <hueffner at informatik dot uni-tuebingen dot de>
To: Graham Stott <graham dot stott at btinternet dot com>
Cc: Ron Flory <ron dot flory at adtran dot com>, gcc-bugs at gcc dot gnu dot org,"Ron Flory, Home" <rjflory at mchsi dot com>
Date: Fri, 18 Jun 2004 16:33:11 +0200
Subject: Re: pointer post-incr problem with GCC 3.3.3 ??
References: <20040618141140.64755.qmail@web86108.mail.ukl.yahoo.com><87r7sdlzet.fsf@informatik.uni-tuebingen.de>

Falk Hueffner <hueffner@informatik.uni-tuebingen.de> writes:

> Graham Stott <graham.stott@btinternet.com> writes:
>
>>>           *(ptr++) = toupper(*ptr);
>>> 
>>>   I would assert these two code frags are functionally identical.
>>>
>> Nope your assertion is wrong.
>>
>> Read up on "sequence points" and you'll undersrand why. 
>
> I don't see this. Can you please explain in detail where the violation
> is?

Actually, I think I see it now. "ptr" has its value read before the
modification of "ptr", without an intervening sequence point, and not
only to determine the value to be stored in "ptr".

-- 
	Falk

References:
- Re: pointer post-incr problem with GCC 3.3.3 ??
  - From: Graham Stott
- Re: pointer post-incr problem with GCC 3.3.3 ??
  - From: Falk Hueffner

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]