Messages in this thread | | | Subject | Re: GCC 3.4 and broken inlining. | From | Alexandre Oliva <> | Date | 10 Jul 2004 18:20:19 -0300 |
| |
On Jul 9, 2004, Arjan van de Ven <arjanv@redhat.com> wrote:
>> >> I believe that just adding -funit-at-a-time as a compile option solves >> the problems with inline function body ordering.
> ... except that -funit-at-a-time causes some functions to use more than > 4Kb of *extra* stack, even without CONFIG_4KSTACKS that's a ticking > timebomb of enormous magnitude..
But that's because of excessive inlining. I suppose the abuse of attribute always_inline may very well be the culprit.
-- Alexandre Oliva http://www.ic.unicamp.br/~oliva/ Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org} Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org} - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |