On 11 May 01 at 9:13, Tom Leete wrote:
> > __asm__ __volatile__(
> > "# beginning __up_read\n\t"
> > + " movl %2,%%edx\n\t"
> > LOCK_PREFIX" xadd %%edx,(%%eax)\n\t" /* subtracts 1, returns the old
>value */
> > " js
Petr Vandrovec wrote:
>
> Hi Alan,
> can you apply this patch to next 2.4.4-acX ? This fixes problem with
> gcc3.0 (20010426) unable to compile this under some conditions. As
> __up_write() uses same code ("i" instead of tmp variable), I think
> that you should apply this. It can cause
Petr Vandrovec wrote:
Hi Alan,
can you apply this patch to next 2.4.4-acX ? This fixes problem with
gcc3.0 (20010426) unable to compile this under some conditions. As
__up_write() uses same code (i instead of tmp variable), I think
that you should apply this. It can cause slower
On 11 May 01 at 9:13, Tom Leete wrote:
__asm__ __volatile__(
# beginning __up_read\n\t
+ movl %2,%%edx\n\t
LOCK_PREFIX xadd %%edx,(%%eax)\n\t /* subtracts 1, returns the old
value */
js2f\n\t /* jump if
Hi Alan,
can you apply this patch to next 2.4.4-acX ? This fixes problem with
gcc3.0 (20010426) unable to compile this under some conditions. As
__up_write() uses same code ("i" instead of tmp variable), I think
that you should apply this. It can cause slower code, as gcc cannot
move "movl
Hi Alan,
can you apply this patch to next 2.4.4-acX ? This fixes problem with
gcc3.0 (20010426) unable to compile this under some conditions. As
__up_write() uses same code (i instead of tmp variable), I think
that you should apply this. It can cause slower code, as gcc cannot
move movl
6 matches
Mail list logo