Bug#983807: spring builds with -march=native on amd64

[Sebastian Ramacher]

Control: severity -1 serious

On 2021-03-02 00:37:37 +0100, Markus Koschany wrote:
> Control: severity -1 normal
> 
> Am Dienstag, den 02.03.2021, 01:32 +0200 schrieb Adrian Bunk:
> [...]
> > > I would really like to understand what the current drawback is for our
> > > users.
> > > If you could provide the build flags with march=native and march=x86-64 and
> > > then prove that march=x86-64 prevents some serious issues or makes the
> > > engine
> > > better for users, I would happily apply your patch. Otherwise I am
> > > reluctant to
> > > apply it because there is no current evidence that it improves the package.
> > > The
> > > GCC manual talks about "it _might_" have some drawbacks but it also depends
> > > on
> > > the package. Again where is the concrete drawback for Spring?
> > 
> > The drawback is that Spring does does not work for users whose computer 
> > is not compatible with whatever buildd happened to build your package.
> > 
> > I am adding debian-release to Cc, please discuss with them if you
> > think this would not be a release critical bug.
> 
> I do not think this is a release critical bug. I disagree with you assumptions.
> The package works fine.

Violating the baseline of an architecture is an RC bug. The i386 build
is not usable on non-SSE CPUs. The i386 architecture still supports
those, though.

It's fine to build some parts with -msse if there is runtime detection
and a fallback.

Cheers
-- 
Sebastian Ramacher
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-games-devel/attachments/20210302/c5012d3c/attachment.sig>