From: Al Viro <viro@ftp.linux.org.uk>
To: Andreas Schwab <schwab@suse.de>
Cc: linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] m68k: more workarounds for recent binutils idiocy
Date: Thu, 12 Oct 2006 01:49:44 +0100 [thread overview]
Message-ID: <20061012004944.GF29920@ftp.linux.org.uk> (raw)
In-Reply-To: <jek636o62y.fsf@sykes.suse.de>
On Thu, Oct 12, 2006 at 12:12:05AM +0200, Andreas Schwab wrote:
> Al Viro <viro@ftp.linux.org.uk> writes:
>
> > cretinous thing doesn't believe that (%a0)+ is one macro argument and
> > splits it in two; worked around by quoting the argument...
>
> What version are you using? Works rather fine here with 2.17.
There are two problems; see below for the testcase covering both
.macro a x
.byte 1
.endm
a.x
a %(a0)+
Old binutils (i.e. what Roman's code expects) treat the above as
.byte 1
.byte 1
That behaviour exists in 2.16.1 and earlier. Everything starting at least
with 2.16.90.0.2 and up to current CVS generates
Error: Unknown operator -- statement `a.x' ignored
for line 4. That's the problem dealt with by the first patch (and yes,
current gas from CVS does blow on arch/m68k/math-emu/ as soon as you get
to getuser.l <something>).
_Another_ problem manifests as
Error: too many positional arguments
in line 5. That had been introduced later (in 2.16.91.0.3, if you look at
versions on kernel.org, or 2005-08-08 in mainline) and had been fixed since
then (2.16.91.0.7 or 2006-02-28 in CVS). That's what the second patch
dealt with and yes, I agree that just slapping "don't use those versions
of binutils" in Documentation/Changes is a better variant.
The first problem still needs to be dealt with.
next prev parent reply other threads:[~2006-10-12 0:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 21:13 [PATCH 2/2] m68k: more workarounds for recent binutils idiocy Al Viro
2006-10-11 21:30 ` Roman Zippel
2006-10-11 22:07 ` Al Viro
2006-10-12 0:50 ` Al Viro
2006-10-11 22:12 ` Andreas Schwab
2006-10-12 0:49 ` Al Viro [this message]
2006-10-12 2:24 ` Dave Jones
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=20061012004944.GF29920@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schwab@suse.de \
/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.