Skip to contentSkip to conversation

i386 do_machine_check() is redundant.

PATCH In review Brian Gerst 11 participants 23 messages Sep 28, 2003 – Sep 30, 2003

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 i386 do_machine_check() is redundant.

Use machine_check_vector in the entry code instead.

--
Brian Gerst

arch/i386/kernel/cpu/mcheck/mce.c +0 -5
diff -urN linux-2.6.0-test6/arch/i386/kernel/cpu/mcheck/mce.c linux/arch/i386/kernel/cpu/mcheck/mce.c
@@ -26,11 +26,6 @@
 /* Call the installed machine check handler for this CPU setup. */
 void (*machine_check_vector)(struct pt_regs *, long error_code) = unexpected_machine_check;
 
-asmlinkage void do_machine_check(struct pt_regs * regs, long error_code)
-{
-	machine_check_vector(regs, error_code);
-}
-
 /* This has to be run for each processor */
 void __init mcheck_init(struct cpuinfo_x86 *c)
 {
arch/i386/kernel/entry.S +1 -1
diff -urN linux-2.6.0-test6/arch/i386/kernel/entry.S linux/arch/i386/kernel/entry.S
@@ -595,7 +595,7 @@
 #ifdef CONFIG_X86_MCE
 ENTRY(machine_check)
 	pushl $0
-	pushl $do_machine_check
+	pushl machine_check_vector
 	jmp error_code
 #endif
 
#1 lore raw
Quoted 2 lines · Brian Gerst

Use machine_check_vector in the entry code instead.

This is wrong. You just lost the "asmlinkage" thing, which means that it breaks when asmlinkage matters.

And yes, asmlinkage _can_ matter, even on x86. It disasbles regparm, for one thing, so it makes a huge difference if the kernel is compiled with -mregparm=3 (which used to work, and which I'd love to do, but gcc has often been a tad fragile).

Linus

#2 lore raw
Quoted 5 lines · Linus Torvalds
Quoted 1 line · Brian Gerst

Use machine_check_vector in the entry code instead.

Quoted 9 lines

This is wrong. You just lost the "asmlinkage" thing, which means that it breaks when asmlinkage matters.

And yes, asmlinkage _can_ matter, even on x86. It disasbles regparm, for one thing, so it makes a huge difference if the kernel is compiled with -mregparm=3 (which used to work, and which I'd love to do, but gcc has often been a tad fragile).

Linus

Good point. Wouldn't it just be better to change the few handlers to asmlinkage instead? Having that stub function there is pointless.

--
Brian Gerst

#3 lore raw
Quoted 3 lines · Brian Gerst

Good point. Wouldn't it just be better to change the few handlers to asmlinkage instead? Having that stub function there is pointless.

That would work, yes. One problem is that gcc doesn't do proper type-checking on it, so it's open to problems. But I'd accept the patch.

Linus

#4 lore raw
Quoted 9 lines · Linus Torvalds
Quoted 1 line · Brian Gerst

Good point. Wouldn't it just be better to change the few handlers to asmlinkage instead? Having that stub function there is pointless.

That would work, yes. One problem is that gcc doesn't do proper type-checking on it, so it's open to problems. But I'd accept the patch.

Linus

Updated patch.

--
Brian Gerst

arch/i386/kernel/cpu/mcheck/k7.c +1 -1
diff -urN linux-2.6.0-test6/arch/i386/kernel/cpu/mcheck/k7.c linux/arch/i386/kernel/cpu/mcheck/k7.c
@@ -17,7 +17,7 @@
 #include "mce.h"
 
 /* Machine Check Handler For AMD Athlon/Duron */
-static void k7_machine_check(struct pt_regs * regs, long error_code)
+static asmlinkage void k7_machine_check(struct pt_regs * regs, long error_code)
 {
 	int recover=1;
 	u32 alow, ahigh, high, low;
arch/i386/kernel/cpu/mcheck/mce.c +2 -7
diff -urN linux-2.6.0-test6/arch/i386/kernel/cpu/mcheck/mce.c linux/arch/i386/kernel/cpu/mcheck/mce.c
@@ -18,18 +18,13 @@
 int nr_mce_banks;
 
 /* Handle unconfigured int18 (should never happen) */
-static void unexpected_machine_check(struct pt_regs * regs, long error_code)
+static asmlinkage void unexpected_machine_check(struct pt_regs * regs, long error_code)
 {	
 	printk(KERN_ERR "CPU#%d: Unexpected int18 (Machine Check).\n", smp_processor_id());
 }
 
 /* Call the installed machine check handler for this CPU setup. */
-void (*machine_check_vector)(struct pt_regs *, long error_code) = unexpected_machine_check;
-
-asmlinkage void do_machine_check(struct pt_regs * regs, long error_code)
-{
-	machine_check_vector(regs, error_code);
-}
+void asmlinkage (*machine_check_vector)(struct pt_regs *, long error_code) = unexpected_machine_check;
 
 /* This has to be run for each processor */
 void __init mcheck_init(struct cpuinfo_x86 *c)
arch/i386/kernel/cpu/mcheck/mce.h +1 -1
diff -urN linux-2.6.0-test6/arch/i386/kernel/cpu/mcheck/mce.h linux/arch/i386/kernel/cpu/mcheck/mce.h
@@ -7,7 +7,7 @@
 void winchip_mcheck_init(struct cpuinfo_x86 *c);
 
 /* Call the installed machine check handler for this CPU setup. */
-extern void (*machine_check_vector)(struct pt_regs *, long error_code);
+extern asmlinkage void (*machine_check_vector)(struct pt_regs *, long error_code);
 
 extern int mce_disabled __initdata;
 extern int nr_mce_banks;
arch/i386/kernel/cpu/mcheck/p4.c +1 -1
diff -urN linux-2.6.0-test6/arch/i386/kernel/cpu/mcheck/p4.c linux/arch/i386/kernel/cpu/mcheck/p4.c
@@ -148,7 +148,7 @@
 	return mce_num_extended_msrs;
 }
 
-static void intel_machine_check(struct pt_regs * regs, long error_code)
+static asmlinkage void intel_machine_check(struct pt_regs * regs, long error_code)
 {
 	int recover=1;
 	u32 alow, ahigh, high, low;
arch/i386/kernel/cpu/mcheck/p5.c +1 -1
diff -urN linux-2.6.0-test6/arch/i386/kernel/cpu/mcheck/p5.c linux/arch/i386/kernel/cpu/mcheck/p5.c
@@ -16,7 +16,7 @@
 #include "mce.h"
 
 /* Machine check handler for Pentium class Intel */
-static void pentium_machine_check(struct pt_regs * regs, long error_code)
+static asmlinkage void pentium_machine_check(struct pt_regs * regs, long error_code)
 {
 	u32 loaddr, hi, lotype;
 	rdmsr(MSR_IA32_P5_MC_ADDR, loaddr, hi);
arch/i386/kernel/cpu/mcheck/p6.c +1 -1
diff -urN linux-2.6.0-test6/arch/i386/kernel/cpu/mcheck/p6.c linux/arch/i386/kernel/cpu/mcheck/p6.c
@@ -16,7 +16,7 @@
 #include "mce.h"
 
 /* Machine Check Handler For PII/PIII */
-static void intel_machine_check(struct pt_regs * regs, long error_code)
+static asmlinkage void intel_machine_check(struct pt_regs * regs, long error_code)
 {
 	int recover=1;
 	u32 alow, ahigh, high, low;
arch/i386/kernel/cpu/mcheck/winchip.c +1 -1
diff -urN linux-2.6.0-test6/arch/i386/kernel/cpu/mcheck/winchip.c linux/arch/i386/kernel/cpu/mcheck/winchip.c
@@ -15,7 +15,7 @@
 #include "mce.h"
 
 /* Machine check handler for WinChip C6 */
-static void winchip_machine_check(struct pt_regs * regs, long error_code)
+static asmlinkage void winchip_machine_check(struct pt_regs * regs, long error_code)
 {
 	printk(KERN_EMERG "CPU0: Machine Check Exception.\n");
 }
arch/i386/kernel/entry.S +1 -1
diff -urN linux-2.6.0-test6/arch/i386/kernel/entry.S linux/arch/i386/kernel/entry.S
@@ -595,7 +595,7 @@
 #ifdef CONFIG_X86_MCE
 ENTRY(machine_check)
 	pushl $0
-	pushl $do_machine_check
+	pushl machine_check_vector
 	jmp error_code
 #endif
 
#5 lore raw
In reply to Linus Torvalds
Quoted 11 lines · Linus Torvalds
Quoted 2 lines · Brian Gerst

Use machine_check_vector in the entry code instead.

This is wrong. You just lost the "asmlinkage" thing, which means that it breaks when asmlinkage matters.

And yes, asmlinkage _can_ matter, even on x86. It disasbles regparm, for one thing, so it makes a huge difference if the kernel is compiled with -mregparm=3 (which used to work, and which I'd love to do, but gcc has often been a tad fragile).

gcc 3.2 and later are supposed to be ok (eg during 3.2 development a long standing bug with regparm was fixed and now is believed to work)... since our makefiles check gcc version already... this can be made gcc version dependent as well for sure..

#6 lore raw
Quoted 10 lines · Arjan van de Ven
Quoted 5 lines

And yes, asmlinkage _can_ matter, even on x86. It disasbles regparm, for one thing, so it makes a huge difference if the kernel is compiled with -mregparm=3 (which used to work, and which I'd love to do, but gcc has often been a tad fragile).

gcc 3.2 and later are supposed to be ok (eg during 3.2 development a long standing bug with regparm was fixed and now is believed to work)... since our makefiles check gcc version already... this can be made gcc version dependent as well for sure..

Has anybody checked out whether the kernel works with -mregparm=3? I forget who did a lot of the work on it originally, and it certainly _used_ to work fine. The improvements to both code size and performance were, if I remember correctly, measurable but not huge.

One worry (apart from just broken compilers and missing "asmlinkage" annotations) is that having compiler-version-dependent calling conventions makes for another variable to take into account when chasing down bugs and worrying about things like the Nvidia module etc. So it's probably not worth doing unless the advantages are clear.

Linus

#7 lore raw
Quoted 4 lines · Linus Torvalds

Has anybody checked out whether the kernel works with -mregparm=3? I forget who did a lot of the work on it originally, and it certainly _used_ to work fine. The improvements to both code size and performance were, if I remember correctly, measurable but not huge.

That jibes with what I would expect (I missed the older threads, but was nonetheless toying with this idea myself)...

Function arguments on the stack are likely to be in L1 cache anyway, so accessing arguments is already pretty cheap. And storing the parameters in registers might increase the number of spills slightly, for cases, where an argument isn't used much, or at all.

Ideally unit-at-a-time could figure out the optimal -mregparm value :)

Quoted 5 lines

One worry (apart from just broken compilers and missing "asmlinkage" annotations) is that having compiler-version-dependent calling conventions makes for another variable to take into account when chasing down bugs and worrying about things like the Nvidia module etc. So it's probably not worth doing unless the advantages are clear.

Well... even with completely open source, you're never gonna have a working system with modules built using compiler versions and options that differ from the main kernel image. In the past, changing compiler versions would definitely affect the module interfaces adversely.

So while I agree with your overall conservatism, worrying about supporting miscompiled modules is the road to Hades...

Jeff

#8 lore raw

-mregparm=3 (was Re: [PATCH] i386 do_machine_check() is redundant.

In reply to Linus Torvalds
Quoted 4 lines · Linus Torvalds

Has anybody checked out whether the kernel works with -mregparm=3? I forget who did a lot of the work on it originally, and it certainly _used_ to work fine. The improvements to both code size and performance were, if I remember correctly, measurable but not huge.

It works well enough that my laptop made it to initlevel 3. The code size wasn't drastically smaller (perhaps another 2-3% but I already compile with -Os). The system "felt" snappier, but I have no benchmark numbers to give. I could probably get some numbers if anybody cares, but there's a showstopper for me - I can't make it to initlevel 5 easily:

Quoted 5 lines

One worry (apart from just broken compilers and missing "asmlinkage" annotations) is that having compiler-version-dependent calling conventions makes for another variable to take into account when chasing down bugs and worrying about things like the Nvidia module etc. So it's probably not worth doing unless the advantages are clear.

Quite correct - even after recompiling the sourced portions of the NVidia driver, it dies a horrid death on 'insmod' when the closed-source portion passes a parameter on the stack and the open side expects the value in a register, and follows the register value to a quick death....

Yes, yes, I know, I could re-try with the open-source nv driver instead of the closed-source NVidia driver - but the open-source one costs me more in performance (as it's unaccelerated) than the mregparm=3 is likely to get me back....

#9 lore raw

Re: -mregparm=3 (was Re: [PATCH] i386 do_machine_check() is redundant.

Quoted 5 lines · [email protected] wrote:

Quite correct - even after recompiling the sourced portions of the NVidia driver, it dies a horrid death on 'insmod' when the closed-source portion passes a parameter on the stack and the open side expects the value in a register, and follows the register value to a quick death....

Nvidia can fix this easily. Either by having several versions of their closed-source thing, or by having a open "interface" that uses nvidia's calling convention for talking to their proprietary binary code, and whatever the kernel uses for talking to the kernel. That's the price of binary modules -
One extra level of indirection, or a bunch of different modules. Of course there are plenty of other cards without
such problems.

Helge Hafting

#10 lore raw

Re: -mregparm=3 (was Re: [PATCH] i386 do_machine_check() is redundant.

Quoted 4 lines · Helge Hafting

Nvidia can fix this easily. Either by having several versions of their closed-source thing, or by having a open "interface" that uses nvidia's calling convention for talking to their proprietary binary code, and whatever the kernel uses for talking to the kernel.

Well, they do have an open interface. I've apparently just not gotten all the __attribute((regparm(0))) in the right places yet. ;)

#11 lore raw

Re: -mregparm=3 (was Re: [PATCH] i386 do_machine_check() is redundant.

Quoted 3 lines · On Tue, 30 Sep 2003 [email protected] wrote:

Well, they do have an open interface. I've apparently just not gotten all the __attribute((regparm(0))) in the right places yet. ;)

They may have some places inside the binary part that call directly out to the kernel, and use the wrong calling conventions.

Linus

#12 lore raw

-mregparm=3 (was Re: [PATCH] i386 do_machine_check() is redundant.

In reply to Arjan van de Ven
Quoted 10 lines
Quoted 9 lines
Quoted 1 line

Use machine_check_vector in the entry code instead.

This is wrong. You just lost the "asmlinkage" thing, which means that it breaks when asmlinkage matters.

And yes, asmlinkage _can_ matter, even on x86. It disasbles regparm, for one thing, so it makes a huge difference if the kernel is compiled with -mregparm=3 (which used to work, and which I'd love to do, but gcc has often been a tad fragile).

Quoted 4 lines

gcc 3.2 and later are supposed to be ok (eg during 3.2 development a long standing bug with regparm was fixed and now is believed to work)... since our makefiles check gcc version already... this can be made gcc version dependent as well for sure..

They are still buggy. gcc 3.3.1 miscompiles itself with -mregparm=3 (without -O or -O2 it works). (I am too lazy to spend several days trying to find exactly which function in gcc was miscompiled, maybe I do it one day). gcc 2.95.3 compiles gcc 3.3.1 with -mregparm=3 -O2 correctly. gcc 3.4 doesn't seem to be better.

gcc 2.7.2.3 has totally broken -mregparm=3, even quite simple programs fail.

Mikulas

#13 lore raw

Re: -mregparm=3 (was Re: [PATCH] i386 do_machine_check() is redundant.

Quoted 15 lines · Mikulas Patocka
Quoted 10 lines
Quoted 9 lines
Quoted 1 line

Use machine_check_vector in the entry code instead.

This is wrong. You just lost the "asmlinkage" thing, which means that it breaks when asmlinkage matters.

And yes, asmlinkage _can_ matter, even on x86. It disasbles regparm, for one thing, so it makes a huge difference if the kernel is compiled with -mregparm=3 (which used to work, and which I'd love to do, but gcc has often been a tad fragile).

Quoted 4 lines

gcc 3.2 and later are supposed to be ok (eg during 3.2 development a long standing bug with regparm was fixed and now is believed to work)... since our makefiles check gcc version already... this can be made gcc version dependent as well for sure..

Quoted 8 lines

They are still buggy. gcc 3.3.1 miscompiles itself with -mregparm=3 (without -O or -O2 it works). (I am too lazy to spend several days trying to find exactly which function in gcc was miscompiled, maybe I do it one day). gcc 2.95.3 compiles gcc 3.3.1 with -mregparm=3 -O2 correctly. gcc 3.4 doesn't seem to be better.

gcc 2.7.2.3 has totally broken -mregparm=3, even quite simple programs fail.

You can't build GCC with -mregparm=3. It changes the interface to system functions. So unless your libc happened to be built with -mregparm=3, and extensively hacked to expect arguments in registers to the assembly stubs, it can't work.

It's interesting for kernel code, whole distributions, or things which are careful to have a glue layer.

Signature · 2 lines
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer
#14 lore raw

Re: -mregparm=3 (was Re: [PATCH] i386 do_machine_check() is redundant.

Quoted 22 lines · Daniel Jacobowitz
Quoted 21 lines · Mikulas Patocka
Quoted 10 lines
Quoted 9 lines
Quoted 1 line

Use machine_check_vector in the entry code instead.

This is wrong. You just lost the "asmlinkage" thing, which means that it breaks when asmlinkage matters.

And yes, asmlinkage _can_ matter, even on x86. It disasbles regparm, for one thing, so it makes a huge difference if the kernel is compiled with -mregparm=3 (which used to work, and which I'd love to do, but gcc has often been a tad fragile).

Quoted 4 lines

gcc 3.2 and later are supposed to be ok (eg during 3.2 development a long standing bug with regparm was fixed and now is believed to work)... since our makefiles check gcc version already... this can be made gcc version dependent as well for sure..

They are still buggy. gcc 3.3.1 miscompiles itself with -mregparm=3 (without -O or -O2 it works). (I am too lazy to spend several days trying to find exactly which function in gcc was miscompiled, maybe I do it one day). gcc 2.95.3 compiles gcc 3.3.1 with -mregparm=3 -O2 correctly. gcc 3.4 doesn't seem to be better.

Quoted 7 lines
Quoted 2 lines

gcc 2.7.2.3 has totally broken -mregparm=3, even quite simple programs fail.

You can't build GCC with -mregparm=3. It changes the interface to system functions. So unless your libc happened to be built with -mregparm=3, and extensively hacked to expect arguments in registers to the assembly stubs, it can't work.

Of course I linked it with libc compiled with regparm=3.

Quoted 2 lines

It's interesting for kernel code, whole distributions, or things which are careful to have a glue layer.

BTW. libc headers surround all function parameters with __P, like extern int printf __P ((__const char* __format, ...));

so you can change in include/sys/cdefs.h
#define __P(x) x
into
#define __P(x) x __attribute__((regparm(0)))

and compile programs with -mregparm=3 -ffreestanding even on normal linux distribution. I didn't try it for larger program, for simple it works. (it works as long as program doesn't call libc function via pointer to function).

(without -ffreestanding gcc sometimes emits calls to library functions on its own, and uses calling convention from command line, not convention from prototype).

Mikulas

#15 lore raw

Re: -mregparm=3 (was Re: [PATCH] i386 do_machine_check() is redundant.

Quoted 29 lines · Mikulas Patocka
Quoted 25 lines · Daniel Jacobowitz
Quoted 23 lines · Mikulas Patocka
Quoted 10 lines
Quoted 9 lines
Quoted 1 line

Use machine_check_vector in the entry code instead.

This is wrong. You just lost the "asmlinkage" thing, which means that it breaks when asmlinkage matters.

And yes, asmlinkage _can_ matter, even on x86. It disasbles regparm, for one thing, so it makes a huge difference if the kernel is compiled with -mregparm=3 (which used to work, and which I'd love to do, but gcc has often been a tad fragile).

Quoted 4 lines

gcc 3.2 and later are supposed to be ok (eg during 3.2 development a long standing bug with regparm was fixed and now is believed to work)... since our makefiles check gcc version already... this can be made gcc version dependent as well for sure..

They are still buggy. gcc 3.3.1 miscompiles itself with -mregparm=3 (without -O or -O2 it works). (I am too lazy to spend several days trying to find exactly which function in gcc was miscompiled, maybe I do it one day). gcc 2.95.3 compiles gcc 3.3.1 with -mregparm=3 -O2 correctly. gcc 3.4 doesn't seem to be better.

gcc 2.7.2.3 has totally broken -mregparm=3, even quite simple programs fail.

Quoted 6 lines
Quoted 4 lines

You can't build GCC with -mregparm=3. It changes the interface to system functions. So unless your libc happened to be built with -mregparm=3, and extensively hacked to expect arguments in registers to the assembly stubs, it can't work.

Of course I linked it with libc compiled with regparm=3.

Did you also hack all the syscall wrappers and hand-coded assembly routines? For instance, mmap won't work.

Signature · 2 lines
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer
#16 lore raw

Re: -mregparm=3 (was Re: [PATCH] i386 do_machine_check() is redundant.

Quoted 35 lines · Daniel Jacobowitz
Quoted 34 lines · Mikulas Patocka
Quoted 29 lines · Daniel Jacobowitz
Quoted 15 lines · Mikulas Patocka
Quoted 10 lines
Quoted 9 lines
Quoted 1 line

Use machine_check_vector in the entry code instead.

This is wrong. You just lost the "asmlinkage" thing, which means that it breaks when asmlinkage matters.

And yes, asmlinkage _can_ matter, even on x86. It disasbles regparm, for one thing, so it makes a huge difference if the kernel is compiled with -mregparm=3 (which used to work, and which I'd love to do, but gcc has often been a tad fragile).

Quoted 4 lines

gcc 3.2 and later are supposed to be ok (eg during 3.2 development a long standing bug with regparm was fixed and now is believed to work)... since our makefiles check gcc version already... this can be made gcc version dependent as well for sure..

Quoted 8 lines

They are still buggy. gcc 3.3.1 miscompiles itself with -mregparm=3 (without -O or -O2 it works). (I am too lazy to spend several days trying to find exactly which function in gcc was miscompiled, maybe I do it one day). gcc 2.95.3 compiles gcc 3.3.1 with -mregparm=3 -O2 correctly. gcc 3.4 doesn't seem to be better.

gcc 2.7.2.3 has totally broken -mregparm=3, even quite simple programs fail.

You can't build GCC with -mregparm=3. It changes the interface to system functions. So unless your libc happened to be built with -mregparm=3, and extensively hacked to expect arguments in registers to the assembly stubs, it can't work.

Quoted 4 lines
Quoted 1 line

Of course I linked it with libc compiled with regparm=3.

Did you also hack all the syscall wrappers and hand-coded assembly routines? For instance, mmap won't work.

It's not linux glibc, it's freebsd libc. And many things don't work there yet, that's why I don't release it.

Mikulas

#17 lore raw

Re: -mregparm=3 (was Re: [PATCH] i386 do_machine_check() is redundant.

In reply to Mikulas Patocka
Quoted 5 lines · Mikulas Patocka
Quoted 2 lines

It's interesting for kernel code, whole distributions, or things which are careful to have a glue layer.

BTW. libc headers surround all function parameters with __P, like extern int printf __P ((__const char* __format, ...));

s/surround/used to &/

Jakub

#18 lore raw

Re: -mregparm=3 (was Re: [PATCH] i386 do_machine_check() is redundant.

In reply to Mikulas Patocka

Folks compiling the kernel with -mregparm=3 should also try -mregparm=2, -mregparm=1 and combinations with -mrtd if you want to find the smallest/fastest.

A long time ago, for a game written mostly in C++, I found the sweet spot at -mregparm=1 -mrtd.

Enjoy,
-- Jamie

#19 lore raw

Re: -mregparm=3 (was Re: [PATCH] i386 do_machine_check() is redundant.

In reply to Mikulas Patocka
Quoted 4 lines · Mikulas Patocka

and compile programs with -mregparm=3 -ffreestanding even on normal linux distribution. I didn't try it for larger program, for simple it works. (it works as long as program doesn't call libc function via pointer to function).

I discovered that -test6-mm1 doesn't build with -ffreestanding with gcc 3.3.1, for an odd reason: when I specify -ffreestanding, it generates 'call abs' calls where it was able to do it inline otherwise. -ffreestanding says there's no library, so it can't inline the library call (which leaves no external call to 'abs()').

#20 lore raw

Re: -mregparm=3 (was Re: [PATCH] i386 do_machine_check() is redundant.

Quoted 4 lines · On Tue, 2003-09-30 at 00:49, [email protected] wrote:

I discovered that -test6-mm1 doesn't build with -ffreestanding with gcc 3.3.1, for an odd reason: when I specify -ffreestanding, it generates 'call abs' calls where it was able to do it inline otherwise. -ffreestanding says there's no library, so it can't inline the library call (which leaves no external call to 'abs()').

Hm, we may need to do something like:

	#define abs(n)	 __builtin_abs((n))

because -ffreestanding implies -fno-builtin, which disables use of built-in functions that do not begin with __builtin.

Robert Love

#21 lore raw

Re: -mregparm=3 (was Re: [PATCH] i386 do_machine_check() is redundant.

Quoted 6 lines · Robert Love

Hm, we may need to do something like:

	#define abs(n)	 __builtin_abs((n))

because -ffreestanding implies -fno-builtin, which disables use of built-in functions that do not begin with __builtin.

Well, abs() is the only one I tripped over in my config. I'm sure there's others lurking elsewhere in the kernel tree.

The bigger question is whether a patch to support -ffreestanding would be a good idea - with proper use of the __builtin_* stuff it *should* work, and it will hopefully cause better kernel code hygiene..

#22 lore raw

Re: -mregparm=3 (was Re: [PATCH] i386 do_machine_check() is redundant.

Quoted 2 lines · On Tue, 2003-09-30 at 10:37, [email protected] wrote:

Well, abs() is the only one I tripped over in my config. I'm sure there's others lurking elsewhere in the kernel tree.

There are not _too_ many builtins. abs, strcpy, et cetera ...

Quoted 3 lines

The bigger question is whether a patch to support -ffreestanding would be a good idea - with proper use of the __builtin_* stuff it *should* work, and it will hopefully cause better kernel code hygiene..

I agree. We should go for it.

Robert Love