Re: [PATCH 1/1] threads_max: Simple lockout prevention patch

On Mon, 2006-04-24 at 17:46 +0300, Al Boldi wrote:
> But -O3 creates faster code w/ some strange flaws like failing nfs-boot.
> Maybe that's fixed in the latest gcc, but gcc-3.2.2 was exhibiting this bug.
> So this doesn't really help a developer to be confident about compiler 
> optimization, thus taking the safe route for performance sensitive 
> code-paths.

Are you talking about a real GCC bug which you must work around? If not,
please don't obfuscate the code for no good reason.

				Pekka

-
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/

---

• References:
  • Re: [PATCH 1/1] threads_max: Simple lockout prevention patch
    • From: Al Boldi <[email protected]>
  • Re: [PATCH 1/1] threads_max: Simple lockout prevention patch
    • From: Pekka Enberg <[email protected]>
  • Re: [PATCH 1/1] threads_max: Simple lockout prevention patch
    • From: Al Boldi <[email protected]>

• Prev by Date: Re: [RFC] [PATCH] Make ACPI button driver an input device
• Next by Date: Re: [Alsa-devel] Re: ALSA regression: oops on shutdown
• Previous by thread: Re: [PATCH 1/1] threads_max: Simple lockout prevention patch
• Next by thread: Re: [PATCH 1/1] threads_max: Simple lockout prevention patch
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]