Changes between Initial Version and Version 1 of Ticket #56373, comment 7


Ignore:
Timestamp:
Apr 28, 2018, 4:24:12 PM (6 years ago)
Author:
jwhowarth
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #56373, comment 7

    initial v1  
    33[https://wiki.gentoo.org/wiki/Project:Python/Strict_aliasing]
    44
    5 However, this differs from the reason we are using it now in pymol which is due to a clang bug causing one of the source files to crash the compiler when -fstricti-aliasing. In general, one would like to avoid -fno-strict-aliasing as it can limit optimization options for the compiler. However considering that the alternative is to compile with no optimization at all, it is a reasonable trade-off here.
     5However, this differs from the reason we are using it now in pymol which is due to a clang bug causing one of the source files to crash the compiler when -fstricti-aliasing Is invoked. In general, one would like to avoid -fno-strict-aliasing as it can limit optimization options for the compiler. However considering that the alternative is to compile with no optimization at all, it is a reasonable trade-off here.
    66
    77A reasonable explanation of strict aliasing can be found at [https://cellperformance.beyond3d.com/articles/2006/06/understanding-strict-aliasing.html]