Segher Boessenkool wrote: > >> I'm a bit surprised about the claim w.r.t. -fno-unit-at-a-time (although >> I guess that is the default and one would thus typically not see this.) > > -fno-unit-at-a-time is the default on three year old compilers, > yes. Newer compilers have unit-at-a-time enabled by default. > As I said, never mind. "Unit at a time" does something totally different from what I somehow had gotten into my head it did. -hpa - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [x86 setup 13/33] Header file to produce 16-bit code with gcc
- From: "Pawel Dziepak" <[email protected]>
- Re: [x86 setup 13/33] Header file to produce 16-bit code with gcc
- References:
- x86 setup code rewrite in C
- From: "H. Peter Anvin" <[email protected]>
- [x86 setup 13/33] Header file to produce 16-bit code with gcc
- From: "H. Peter Anvin" <[email protected]>
- Re: [x86 setup 13/33] Header file to produce 16-bit code with gcc
- From: Segher Boessenkool <[email protected]>
- Re: [x86 setup 13/33] Header file to produce 16-bit code with gcc
- From: Andi Kleen <[email protected]>
- Re: [x86 setup 13/33] Header file to produce 16-bit code with gcc
- From: "H. Peter Anvin" <[email protected]>
- Re: [x86 setup 13/33] Header file to produce 16-bit code with gcc
- From: Segher Boessenkool <[email protected]>
- x86 setup code rewrite in C
- Prev by Date: Re: [PATCH] x86_64 - Use non locked version for local_cmpxchg()
- Next by Date: Re: [x86 setup 16/33] String-handling functions for the new x86 setup code.
- Previous by thread: Re: [x86 setup 13/33] Header file to produce 16-bit code with gcc
- Next by thread: Re: [x86 setup 13/33] Header file to produce 16-bit code with gcc
- Index(es):
 |