[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: current development

From: Joseph Heled
Subject: Re: current development
Date: Wed, 4 Dec 2019 10:54:11 +1300

I fully appreciate your plight as a package maintainer, but I think
that users which use rollouts, a quite important GNUBG feature, care a
*lot* about speed.

Perhaps the GNUBG code can be structured in a way that it can be
compiled with all those "advance features", yet they are used *only*
in rollouts and so everything else works on older systems?

Is that possible or am I just showing my ignorance?


On Wed, 4 Dec 2019 at 10:42, Russ Allbery <address@hidden> wrote:
> Joseph Heled <address@hidden> writes:
> > My cpu (i7) has sse4 and avx2 support. Compiling from source is not the
> > right answer in general. Users should get this in the compiled package,
> > no?
> The Ubuntu packaging is a copy of the Debian packaging, which I maintain.
> The Debian packaging uses the most conservative CPU settings to ensure
> that gnubg can run on every platform that Debian supports.  I'm
> intentionally sacrificing some speed to avoid the problem where someone
> installs the gnubg package and then the binary won't run at all.
> My (possibly erroneous) perception is that most users of the package don't
> care that much about pure speed.
> Trying to build the binary multiple times with different compiler flags
> and select an appropriate version for the local CPU at runtime was more
> work than I had time or energy to do, and felt like overkill.
> --
> Russ Allbery (address@hidden)             <https://www.eyrie.org/~eagle/>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]