Updated to gcc version 5 #62
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The update takes place not because we *depend* on anything that is new in gcc-5, but it's still good practice to upgrade early to find out any potential issues, and also because gcc 5 will sooner or later be the default (presumably). In this case, the upgrade was very smooth and trouble-free, which is nice. ---- Details: * Vagrantfile: Updated to Debian 9 (a.k.a. stretch), so we can get the gcc-5 package (it't not available in jessie, i.e. Debian 8). * rakelib/common_settings.rake: Use gcc-5 as the compiler by default. * Rakefile: Don't build the iso_image task by default, since it will have garbage content in that case. It doesn't make sense to build it before the binaries have been installed in the right place. * storm/ia32/dispatch.c: gcc-5 is more aggressive in its optimizations, so the variable gets optimized away if we provide it as static.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The update takes place not because we depend on anything that is new in gcc-5, but it's still good practice to upgrade early to find out any potential issues, and also because gcc 5 will sooner or later be the default (presumably). In this case, the upgrade was very smooth and trouble-free, which is nice.
Details: