On 2018-05-21, Peter Hessler wrote:
> i386 and amd64 are different platforms, so of course you get different
> packages.
>
> Within the same platform, all binaries that are built should run on all
> possible members of that platform.
>
> So, code will be compiled WITHOUT AVX support, unless it ca
Okey, thanks both for the help!
Elias.
>> do I still get the same package ?
Yes.
cc(1) does not use microarchitecture-specific features unless you provide
"-march" explicitly.
Other BSDs do it, but OpenBSD does not. So, cc(1) only knows that you are
building something for amd64.
There should not be any difference between nehalem and co
i386 and amd64 are different platforms, so of course you get different packages.
Within the same platform, all binaries that are built should run on all
possible members of that platform.
So, code will be compiled WITHOUT AVX support, unless it can be detected
at runtime (e.g. mplayer/ffmpeg). I
Hi,
I understand that about the builds and packages.
I will re write my question in another form:
If I build, say, firefox on a i386 machine I get a package, and
another if I build firefox on amd64, they differ.
If I build firefox on an amd64 machine WITHOUT AVX support I get a
package, if now I bu
Hello.
OpenBSD team does not recommend to build anything that exists in packages.
>>If so, building from ports would produce a different code?
In most cases ports are not aware of your microarchitecture.
See my question and Theo's answer.
https://www.mail-archive.com/misc@openbsd.org/msg160878.h
Hi,
I have this question in my mind for a time now, if I download OpenBSD
and install all the applications from packages do OpenBSD and the apps
use for example AVX512 ? I mean, if I understand correctly, the
compiler should optimize the code for a given set of instructions,
given that, for example
7 matches
Mail list logo
