[Numpy-discussion] Ia `-fno-strict-aliasing` still required?

Neal Becker ndbecker2 at gmail.com
Fri Jan 4 13:24:47 EST 2019


Define "doing fine", does it pass all tests?

On Fri, Jan 4, 2019 at 12:36 PM Charles R Harris <charlesr.harris at gmail.com>
wrote:

> Hi All,
>
> Just asking if the `-fno-strict-aliasing` flag is still required for gcc.
> Supposedly `-fstrict-aliasing` is enabled by default with optimization
> levels >= `-O2` and that used to result in errors. However, I have noticed
> that numpy wheels are being built without the `-fno-strict-aliasing` flag
> and doing fine. Same on my local machine. So maybe the compiler has gotten
> better at knowing when pointers may be aliased? I cannot find informative
> documentation on how `-fstrict-aliasing` is actually implemented, so
> thought I'd ask here if someone knows more about it.
>
> Chuck
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190104/c6296aba/attachment.html>


More information about the NumPy-Discussion mailing list