From: Herbert Rosmanith <kernel@wildsau.enemy.org>
Message-Id: <200505231125.j4NBPQoZ018751@wildsau.enemy.org>
Subject: Re: [PATCH] binutils-2.16.90.0.3: can't compile 2.4.30
In-Reply-To: <200505231113.j4NBDxLp018742@wildsau.enemy.org>
To: linux-kernel@vger.kernel.org
Date: Mon, 23 May 2005 13:25:26 +0200 (MET DST)
CC: Herbert Rosmanith <kernel@wildsau.enemy.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1011
Lines: 36

> bash-2.05# cat test.nasm 
> 
> bits    32
> section .text
> 
>         mov     eax,ds
>         mov     ds,eax
 
> of course, it's still not possible to move 32 bits into a segreg,
> so what? the processor will silently ignore the upper word, I guess.

oops ... as doesn't complain about that either .... the error is produced
when moving a segreg to a 32bit memory location, e.g.:

(nasm)
        mov     ds,long [ebx]
(as)
#APP
        movl %ds,636(%ebx)
        movl %gs,640(%ebx)
#NO_APP

neither nasm nor as do like that. I wonder which code the previous
binutils produced in that case?

sorry for the superfluos posting, I really should brush up on my assembly;-)
the consequence still is to apply the patches to the kernel.

best regards,
herbert rosmanith

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/