Re: [PATCH 6/8] i386: bitops: Don't mark memory as clobbered unnecessarily

On Mon, 23 Jul 2007, Satyam Sharma wrote:
> 
> The goal is to let gcc generate good, beautiful, optimized code.

No. The point is to let gcc generate *correct* code.

It's either "=m" together with "memory", or it's "+m".

You just introduced a bug.

		Linus
-
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: [PATCH 6/8] i386: bitops: Don't mark memory as clobbered unnecessarily
    • From: Benjamin Herrenschmidt <[email protected]>

• References:
  • [PATCH 0/8] i386: bitops: Cleanup, sanitize, optimize
    • From: Satyam Sharma <[email protected]>
  • [PATCH 6/8] i386: bitops: Don't mark memory as clobbered unnecessarily
    • From: Satyam Sharma <[email protected]>

• Prev by Date: Re: [PATCH 4/8] i386: bitops: Kill volatile-casting of memory addresses
• Next by Date: Re: [PATCH 2/8] i386: bitops: Rectify bogus "Ir" constraints
• Previous by thread: Re: [PATCH 6/8] i386: bitops: Don't mark memory as clobbered unnecessarily
• Next by thread: Re: [PATCH 6/8] i386: bitops: Don't mark memory as clobbered unnecessarily
• 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]