>"Benjamin C.R. LaHaise" <blah@kvack.org> writes:
>
>> <sigh> It's a wonderful idea that really cuts down on the cost of function
>> calls quite a bit, but alas, neither gcc nor egcs work even vaguely
>> reliably with the -mregparm option.
>
>I'm using regparm (using attributes, though) in glibc 2.1 on Intel and
>it does work. Don't spread these wrong information.
Do you suggest me to patch the kernel to be compiled with -regparm=3? I' d
like to know if it will be only a waste of time (as suggested by
Benjamin).
Also Benjamin are you sure that the bug you have discovered in gcc in the
nex000 driver is not been fixed in 2.8.1? (probably no if it was a real
bug and nobody answered you from gcc-bugs...)
The strange thing is that the kernel crashes also for me but gcc
-regparm=1 doesn' t print any warning during compilation (even if there
are some "m" that should be reverted to "r" in the inline asm though).
-regparm=3 instead don' t compile due some inline asm (but this has to
happen). I am using gcc-2.8.1 (that seems to be fine here BTW, I have only
tried -O2 though).
Andrea[s] Arcangeli
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu