Re: [BUG mm] "fixed" i386 memcpy inlining buggy

I'm having a little difficulty understanding what this is for.  Is it
that gcc's builtin memcpy expander generates bad code, or that older
versions of gcc generate bad code, or what?  gcc generates too much
code?

Andrew.
-
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: memcpy(a,b,CONST) is not inlined by gcc 3.4.1 in Linux kernel
    • From: Denis Vlasenko <[email protected]>
  • [BUG mm] "fixed" i386 memcpy inlining buggy
    • From: Christophe Saout <[email protected]>
  • Re: [BUG mm] "fixed" i386 memcpy inlining buggy
    • From: Denis Vlasenko <[email protected]>
  • Re: [BUG mm] "fixed" i386 memcpy inlining buggy
    • From: Christophe Saout <[email protected]>

• Prev by Date: Re: [OOPS] 2.6.11 - NMI lockup with CFQ scheduler
• Next by Date: Re: [ACPI] Re: It's getting worse: 2.6.12-rc2-mm1 and suspend2ram
• Previous by thread: Re: [BUG mm] "fixed" i386 memcpy inlining buggy
• Next by thread: Re: [BUG mm] "fixed" i386 memcpy inlining buggy
• 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]