public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 09/36] m68k: fix macro syntax to make current binutils happy
Date: Thu, 29 Dec 2005 21:03:36 +0000	[thread overview]
Message-ID: <20051229210336.GJ27946@ftp.linux.org.uk> (raw)
In-Reply-To: <200512262259.19230.zippel@linux-m68k.org>

On Mon, Dec 26, 2005 at 10:59:18PM +0100, Roman Zippel wrote:
> Hi,
> 
> On Thursday 22 December 2005 05:49, Al Viro wrote:
> 
> > recent as(1) doesn't think that . terminates a macro name, so
> > getuser.l is _not_ treated as invoking getuser with .l as the
> > first argument.
> 
> Could you please hold back with the binutils changes? Eventually this should 
> rather be fixed in gas or they have to properly document the expected 
> behaviour, so it doesn't break the next time they change it.

Unfortunately, that one _is_ documented.  BS they've pulled with macro
arguments ("if you have ( in it, forget about sanity and just quote")
is not, but I'm afraid that the only real way to deal with that
properly is to do as(1) from scratch for targets we care about and
make sure it produces binaries identical to gas(1) output on everything
gcc is likely to throw at it.

Alternatively, we could simply stop using as(1) macros and do it in C
preprocessor, or, (much) better yet, m4.  At least those have documented
semantics that is not likely to change at random...

      reply	other threads:[~2005-12-29 21:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-22  4:49 [PATCH 09/36] m68k: fix macro syntax to make current binutils happy Al Viro
2005-12-26 21:59 ` Roman Zippel
2005-12-29 21:03   ` Al Viro [this message]

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=20051229210336.GJ27946@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox