Even when C89 was being drafted, there was a concern for ensuring that compilers could optimize based on non-aliasing assumptions.
-
-
Replying to @RichFelker
C89 3.3 reads "An object shall have its stored value accessed only by an lvalue that has one of the following types:[28]..."
1 reply 0 retweets 0 likes -
Replying to @RichFelker
With footnote 28 as follows: "The intent of this list is to specify those circumstances in which an object may or may not be aliased."
2 replies 0 retweets 0 likes -
Replying to @RichFelker
this doesn't contradict OpenBSD's man page, and I'm not sure what you find funny in it. It says -fstrict-aliasing causes issues…
2 replies 0 retweets 0 likes -
Replying to @volatile_void
Did you mean to reply to this thread and not the OpenBSD one?
1 reply 0 retweets 0 likes -
Replying to @RichFelker
This thread is about the general unawareness that even before C89 there was intent that compilers do non-aliasing-based optimizing
1 reply 0 retweets 0 likes -
-
Replying to @volatile_void @RichFelker
I agree that C89 anticipated a number of optimizations and that developers should perhaps have listened better
1 reply 0 retweets 0 likes
Yes, that was the main point of this thread -- "y'all were warned about this 27 years ago!" :-)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.