.travis.yml: avoid Valgrind bug with '-march=native' #171
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
|
Wow, interesting. Did I miss that in the Travis results of #163? I don't remember seeing any issues. |
|
It seems, #163 has never been built on Travis CI… |
|
Cannot even find a PPA for valgrind 3.10. I rebase my change on this PR :( |
miloyip
added a commit
that referenced
this pull request
Oct 24, 2014
.travis.yml: avoid Valgrind bug with '-march=native'
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 switch in #163 to
-march=nativeexposed a Valgrind bug on the Travis CI machines, see e.g. build 436 and following:Possibly fixed in Valgrind 3.10, see upstream bug https://bugs.kde.org/show_bug.cgi?id=326469.
This pull-request temporarily changes the
-march=nativeflags back to-msse4.2after the generation of the gmake files. I still think that the original change in #163 is reasonable.