Skip to content

Conversation

@giordano
Copy link
Member

@giordano giordano commented Jan 13, 2020

For context, it was reported in
JuliaCI/BaseBenchmarks.jl#253 that dlopening a library
compiled with -Ofast caused the denormal mode to be changed.

This PR disallows using compiler flags that are known to cause troubles.

For context, it was reported in
JuliaCI/BaseBenchmarks.jl#253 that dlopening a library
compiled with `-Ofast` caused the denormal mode to be changed.

This PR disallows using compiler flags that are known to cause troubles.

* Add other unsafe flags suggested by Simon Byrne

Co-Authored-By: Alex Arslan <ararslan@comcast.net>
@staticfloat staticfloat merged commit 512c4a4 into JuliaPackaging:master Jan 15, 2020
@giordano giordano deleted the Ounsafe-fast branch January 15, 2020 19:47
@mreineck
Copy link

There are legitimate use cases for -funsafe-math-optimizations which cannot be achieved by means of any other flag (at least not at the moment). And if the flag is used at compile time, it does not cause any of the nasty effects mentioned at the top. Only its use at link time causes trouble.

Is there a way of stripping the flags in a more selective fashion?

@giordano
Copy link
Member Author

Is there a way of stripping the flags in a more selective fashion?

I don't think we can't really distinguish between compile and linking stage. However, it is possible to allow unsafe flags (although this feature is not documented), if this is necessary and there is the possibility to not break someone else's code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants