[Debian-med-packaging] Bug#776812: usage of -mtune=core2 ? (Was: Bug#776812: vsearch: FTBFS on non-x86: uses non-portable flags)
andreas at an3as.eu
Mon Feb 2 06:51:28 UTC 2015
I have a question regarding a gcc option which was reported as
problematic for other architectures than x86 in #776812:
On Sun, Feb 01, 2015 at 10:48:52PM -0500, Aaron M. Ucko wrote:
> Source: vsearch
> Version: 1.0.7+dfsg-1
> Severity: important
> Justification: fails to build from source
> Builds of vsearch on non-x86 architectures have been failing due to its
> use of the x86-specific compilation flags -msse2 and -mtune=core2.
> -mtune=core2 is okay on x86, but problematic elsewhere.
> As such, could you please rescind the use of -msse2 altogether, and
> either do the same for -mtune=core2 or at minimum use it only on x86?
I have understood that -msse2 should not be used but I wonder what might
be the side effect if I would leave out -mtune=core2 as well. It is
very important to build vsearch with the maximum optimisation for speed
and thus I wonder whether dropping this option is a good idea or whether
I should enable it on i386 and amd64 (the question extends also to
freebsd-i386/freebsd-amd64 once an other issue in freebsd with this
package is solved).
More information about the Debian-med-packaging