[lkml]   [2002]   [Sep]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [BENCHMARK] Corrected gcc3.2 v gcc2.95.3 contest results
Jakub Jelinek <> writes:

> BTW: Have you tried gcc 3.2 with say -finline-limit=2000 too?
> By default gcc 3.2 has for usual C code smaller inlining cutoff, so the IO
> difference might as well be because some important, but big function was
> inlined by 2.95.x and not by 3.2.x. On the other side there is
> __attribute__((always_inline)) which you can use to tell gcc you don't
> want any cutoff for a particular function.

How about using -Winline?

Måns Rullgård
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:29    [W:0.076 / U:4.500 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site