You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although we've enabled -fno-strict-aliasing in #582, I would on principle rather we just didn't have any strict-aliasing violations in our code. But:
I expect the bytestring C code contains little (if any) of the sort of code that actually gets performance wins from -fstrict-aliasing
Although the strict-aliasing-compliant idioms are not uglier than what we are currently doing instead, they are not prettier in any way except that they remove the need to remember that -fno-strict-aliasing has been set.
So this is an extremely-low-priority task.
The text was updated successfully, but these errors were encountered:
Although we've enabled
-fno-strict-aliasing
in #582, I would on principle rather we just didn't have any strict-aliasing violations in our code. But:bytestring
C code contains little (if any) of the sort of code that actually gets performance wins from-fstrict-aliasing
-fno-strict-aliasing
has been set.So this is an extremely-low-priority task.
The text was updated successfully, but these errors were encountered: