From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Herbert Rosmanith <kernel@wildsau.enemy.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.31 & latest binutils: asm-problems still there
Date: Sun, 5 Jun 2005 15:16:32 -0300 [thread overview]
Message-ID: <20050605181632.GA19297@logos.cnet> (raw)
In-Reply-To: <200506040329.j543TWV7029456@wildsau.enemy.org>
On Sat, Jun 04, 2005 at 05:29:31AM +0200, Herbert Rosmanith wrote:
>
> good morning,
>
> I've just tried to compile 2.4.31 and it still doesn't compile
> cleanly with the latest binutils release.
>
> gcc -D__KERNEL__ -I/data/root/linux-2.4.31/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -malign-functions=4 -nostdinc -iwithprefix include -DKBUILD_BASENAME=process -c -o process.o process.c
> {standard input}: Assembler messages:
> {standard input}:750: Error: suffix or operands invalid for `mov'
> {standard input}:751: Error: suffix or operands invalid for `mov'
> {standard input}:845: Error: suffix or operands invalid for `mov'
> {standard input}:846: Error: suffix or operands invalid for `mov'
> {standard input}:897: Error: suffix or operands invalid for `mov'
> {standard input}:898: Error: suffix or operands invalid for `mov'
> {standard input}:900: Error: suffix or operands invalid for `mov'
> {standard input}:912: Error: suffix or operands invalid for `mov'
>
> alessandro suardi told me that this problem is solved using the
> patch from:
> http://www.kernel.org/pub/linux/devel/binutils/linux-2.4-seg-4.patch
>
> which are dated from march (2005-03-27) and therefore, about 3 months
> old.
>
> it's about time this gets into the official kernel. who is in charge
> of it? (it's obviously not sufficient to report to lkml).
Looks OK except that one "movl" conversion was forgotten in
the x86-64 diff:
@@ -609,7 +609,7 @@ struct task_struct *__switch_to(struct t
}
{
unsigned gsindex;
- asm volatile("movl %%gs,%0" : "=g" (gsindex));
+ asm volatile("movl %%gs,%0" : "=r" (gsindex));
if (unlikely((gsindex | next->gsindex) || prev->gs)) {
Who wrote the patch?
next prev parent reply other threads:[~2005-06-05 23:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-04 3:29 2.4.31 & latest binutils: asm-problems still there Herbert Rosmanith
2005-06-05 18:16 ` Marcelo Tosatti [this message]
2005-06-05 23:34 ` Willy Tarreau
2005-06-05 23:49 ` H. J. Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050605181632.GA19297@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=kernel@wildsau.enemy.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.