simonbyrne removed subscribers: jeroen.dobbelaere, carlosgalvezp.
simonbyrne added a comment.
i have no idea. It looks like it may have been resolved in
https://reviews.llvm.org/rL303851? In that case, the NOTE should be removed.
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D30538/new/
carlosgalvezp added a comment.
Herald added a subscriber: jeroen.dobbelaere.
Herald added a project: All.
Hi, is this commit still valid? Why hasn't it been pushed?
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D30538/new/
https://reviews.llvm.org/D30538
simonbyrne updated this revision to Diff 100430.
simonbyrne added a comment.
Fix capitalisation.
https://reviews.llvm.org/D30538
Files:
docs/UsersManual.rst
Index: docs/UsersManual.rst
===
--- docs/UsersManual.rst
+++ docs/User
dim accepted this revision.
dim added a comment.
This revision is now accepted and ready to land.
LGTM, though it would be nice if we implemented gcc's extension for this at
some point... ;)
https://reviews.llvm.org/D30538
___
cfe-commits mailing l
dberlin added a comment.
In https://reviews.llvm.org/D30538#690699, @hans wrote:
> +1 for documenting this, but I have to leave it to the language lawyers for
> how to fomulate it.
>
> > Enables/disables the strict aliasing assumption, which assumes that objects
> > of different types do not sh
hans added a comment.
+1 for documenting this, but I have to leave it to the language lawyers for how
to fomulate it.
> Enables/disables the strict aliasing assumption, which assumes that objects
> of different types do not share the same location in memory.
I think it needs to say incompatibl
On Thu, Mar 02, 2017 at 04:20:47PM +, Simon Byrne via Phabricator via
cfe-commits wrote:
> simonbyrne created this revision.
>
> This is probably good to document, as the behaviour of `-fstrict-aliasing`
> differs from gcc in a quite important way (see
> https://bugs.llvm.org//show_bug.cgi?
hfinkel added inline comments.
Comment at: docs/UsersManual.rst:1106
+
+ NOTE: unlike gcc, clang does not allow "type-punning" by writing and
+ reading from different union members without `-fno-strict-aliasing`
Capitalize Unlike.
https://reviews.llvm.org/D
simonbyrne created this revision.
This is probably good to document, as the behaviour of `-fstrict-aliasing`
differs from gcc in a quite important way (see
https://bugs.llvm.org//show_bug.cgi?id=31928) .
https://reviews.llvm.org/D30538
Files:
docs/UsersManual.rst
Index: docs/UsersManual.r
