-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set build flags differently for release builds #159
Comments
+1 |
Are we sure we need this? The only people that will likely be diving through pyvex code is us anyways, and we can make ad hoc changes to the flags in that scenario. Otherwise, I don't see why we ever want anything but |
Of course not, but I'd like my life to be a little easier... |
If you think you'll save more time building in build profile detection than changing the compiler flags when needed, then it makes sense of course. I'm not so sure that it'll amortize, though. |
if I cared about amortizing profits instead of doing the right thing at all times I would be living my life very very very differently... |
Hahahaha, fair point :-) |
This issue has been marked as |
This issue has been marked as |
This issue has been marked as |
Right now all builds are
-g -O2
, which seems bad. We should probably have some good way to detect the build profile and switch between-g -O0
(maybe-g -O1
?) and-Ofast
or whatever other flags we want for release.The text was updated successfully, but these errors were encountered: