In message <[email protected]>you write:
> Could you please explain the syntax of an earlyclobber (I never heard of it).
> I would undergo the task of patching Linux-Kernel's asms, since I'd like to
> stop the debate about an EGCS/Kernel mismatch. EGCS is a valuable project a nd
> compiling a kernel should not delay using it.
It's pretty simple.
For example strstr would look something like this:
extern inline char * strstr(const char * cs,const char * ct)
register char * __res;
"cld\n\t" "movl %6,%%edi\n\t"
:"=a" (__res), "=&c" (__dummy1), "=&S" (__dummy2) :"0" (0), "1" (0xfffff
fff), "2" (cs),"g" (ct)
Notice how cx and si are no longer in the clobber list. Instead there's
a dummy output operand for each with is marked as an earlyclobber (=&)
of the register class which contains cx and si.
The inputs which must be allocated to cx and si are forced to match
the outputs via the "1" and "2" constraints respectively.
Note that even with that fix, this asm is still has the potential to
cause problems, especially when compiling with -fno-strength-reduce.
The problem is ax, cx, si, dx and di are explicitly used by the insn.
This leaves just bx for reloading.
The general operand "g" (ct) may require 2 reload regs since it might
used an indexed address. Unfortunately only one reload register is
considered available (bx).
This is a problem with the asm, not gcc. Basically when compiling
with -fno-strength-reduce there may not enough registers to handle
this asm, depending on address of "ct".
Changing the constraint for "ct" to be a register will not help since
the compiler would still need to reload the value of ct into the
register to satisfy the register constraint, which still may require
2 reload registers.
You must either rewrite the asm to use one less register or not
compile with -fno-strength-reduce (note -fno-strength-reduce should
not be necessary for gcc-2.8 or egcs).
In fact, its this exact situation that started this whole discussion;
right now the compiler may silently generate incorrect code if it
runs out of registers for an x86 asm that explicitly clobbers registers.
I've got a change which will cause the compiler to issue a fatal error
anytime a clobber overlaps with an input operand or the address of
any operand. This change is likely to expose various problems in
x86 asm statements for Linux since overlapping inputs and outputs
is relatively common.
I've hesitated installing this change because it's going to cause
so many compile time failures for code which currently exists in the
One possibility would be to make the behavior conditional on a switch;
the default behavior right now would be to mimic the old behavior.
Once y'all have had time to fix the problems we could make the more
strict asm checking the default behavior.