Re: [patch 7/7] Make "inline" no longer mandatory for gcc 4.x

Arjan van de Ven <[email protected]> wrote:
>
> if optimizing for size (CONFIG_CC_OPTIMIZE_FOR_SIZE), allow gcc4 compilers
>  to decide what to inline and what not - instead of the kernel forcing gcc
>  to inline all the time. This requires several places that require to be 
>  inlined to be marked as such, previous patches in this series do that.

This one stomps all over more-updates-for-the-gcc-=-32-requirement.patch. 
PLease redo against 2.6.15-mm1 or next -mm?
-
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 7/7] Make "inline" no longer mandatory for gcc 4.x
    • From: Arjan van de Ven <[email protected]>

• References:
  • [patch 1/7] Make __always_inline actually force always inlining
    • From: Arjan van de Ven <[email protected]>
  • [patch 7/7] Make "inline" no longer mandatory for gcc 4.x
    • From: Arjan van de Ven <[email protected]>
  • Re: [patch 7/7] Make "inline" no longer mandatory for gcc 4.x
    • From: Jeff Garzik <[email protected]>
  • Re: [patch 7/7] Make "inline" no longer mandatory for gcc 4.x
    • From: Arjan van de Ven <[email protected]>

• Prev by Date: Re: [PATCH] sched: Fix adverse effects of NFS client on interactive response
• Next by Date: Re: Inclusion of x86_64 memorize ioapic at bootup patch
• Previous by thread: Re: [patch 7/7] Make "inline" no longer mandatory for gcc 4.x
• Next by thread: Re: [patch 7/7] Make "inline" no longer mandatory for gcc 4.x
• 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]