Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Mar 2010 17:28:06 +0100
From:      Ivan Voras <ivoras@freebsd.org>
To:        netch@netch.kiev.ua
Cc:        svn-src-head@freebsd.org, Garrett Cooper <yanefbsd@gmail.com>, svn-src-all@freebsd.org, src-committers@freebsd.org, Xin LI <delphij@freebsd.org>
Subject:   Re: I486_CPU and I586_CPU removed from GENERIC kernel [was Re: svn  commit: r205307 - head/sys/i386/conf]
Message-ID:  <9bbcef731003190928l165c6279p6244f0c97a92600a@mail.gmail.com>
In-Reply-To: <20100319162249.GD67820@netch.kiev.ua>
References:  <7d6fde3d1003182333m336d52fbh987035a21568250d@mail.gmail.com>  <9bbcef731003190913k4f3afbd8mb4e767c40433be8e@mail.gmail.com>  <20100319162249.GD67820@netch.kiev.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
On 19 March 2010 17:22, Valentin Nechayev <netch@netch.kiev.ua> wrote:
> =C2=A0Fri, Mar 19, 2010 at 17:13:00, ivoras wrote about "Re: I486_CPU and=
 I586_CPU removed from GENERIC kernel [was Re: svn commit: r205307 - head/s=
ys/i386/conf]":
>
>> SSE in the userland you mean? Regardless, I don't think there is now
>> reason for compiling everything as for i386. E.g. why not add at least
>> -mtune=3Dgeneric or even also -march=3Di686 to default gcc options?
>>
>> http://gcc.gnu.org/onlinedocs/gcc/i386-and-x86_002d64-Options.html
>
> Having userland compiled with i686 will give the same effect as i686-only
> kernel: it won't boot on machines which doesn't conform to. If it is
> supposed to boot on i486 and higher, no more than -march=3Di486 can be us=
ed.

Yes, this is how I read the change - the move from "i386" to "i686". I
apologize if I got it wrong :)

As it was pointed out earlier - small systems users and designers
probably have special install procedures because of the nature of the
business.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9bbcef731003190928l165c6279p6244f0c97a92600a>