Corinna wrote:
> On Jan 28 01:33, Christopher Faylor wrote:
>> On Fri, Jan 27, 2006 at 03:06:44PM -0700, Eric Blake wrote:
>> >According to Dave Korn on 1/27/2006 9:34 AM:
>> >>Nope, don't worry about it, that's a bit of a red-herring. By default,
>> >>the code gcc generates is good for everythin
On Jan 28 01:33, Christopher Faylor wrote:
> On Fri, Jan 27, 2006 at 03:06:44PM -0700, Eric Blake wrote:
> >According to Dave Korn on 1/27/2006 9:34 AM:
> >>Nope, don't worry about it, that's a bit of a red-herring. By default,
> >>the code gcc generates is good for everything from '486 up. The
>
On Fri, Jan 27, 2006 at 03:06:44PM -0700, Eric Blake wrote:
>According to Dave Korn on 1/27/2006 9:34 AM:
>>Nope, don't worry about it, that's a bit of a red-herring. By default,
>>the code gcc generates is good for everything from '486 up. The
>>instruction scheduling and choice of which instruc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Dave Korn on 1/27/2006 9:34 AM:
> Nope, don't worry about it, that's a bit of a red-herring. By default, the
> code gcc generates is good for everything from '486
> up. The instruction scheduling and choice of which instructions to us
On 27 January 2006 15:36, James McLaughlin wrote:
> Hi,
>
> Cygwin contains several files/folders with names including the string
> "i686-pc-cygwin". I'm using it on an i586, and I've been wondering if I'm
> supposed to be - should I have deduced from this name that there would be
> problems tryi
Hi,
Cygwin contains several files/folders with names
including the string "i686-pc-cygwin". I'm using it on
an i586, and I've been wondering if I'm supposed to be
- should I have deduced from this name that there
would be problems trying to use Cygwin on a 586? (I do
have a few problems when using
6 matches
Mail list logo
