Re: Odd GCC Behavior
Re: Odd GCC Behavior
- Subject: Re: Odd GCC Behavior
- From: Jean-Daniel Dupas <email@hidden>
- Date: Mon, 30 Jun 2008 22:02:43 +0200
Le 30 juin 08 à 21:44, Eli Bach a écrit :
On Jun 30, 2008, at 11:32 AM, J. Aaron Pendergrass wrote:
I'm certainly not trying to get anyone to do my work, merely
pointing out what seemed like a peculiar implementation
and potential source of cross-platform incompatibilities, and
perhaps to gain some insight into exactly what decisions
led to this piece of behavior.
Others have comments on why it may result in significantly different
code for different platforms [heck, may even different optimization
levels]. Just switching from ggc 3.3 to gcc 4.0 on PowerPC could
make it work differently [only in a less noticeable way].
I would argue it's a feature/benefit that it works differently as
often as possible, as I would automatically classify using undefined
compiler behavior as a serious bug.
Wouldn't it be best for your code base that all use of undefined
behavior be removed as soon as possible. The more different it
works hopefully makes the problem more apparent.
Maybe the compiler should warn or even produce an error instead of
generating "random" code with undefined behavior ?
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden