From: Roman Zippel <zippel@linux-m68k.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org,
linux-m68k@vger.kernel.org
Subject: Re: [PATCH 08/41] m68k: fix macro syntax to make current binutils happy
Date: Sun, 8 Jan 2006 18:11:55 +0100 [thread overview]
Message-ID: <200601081811.58669.zippel@linux-m68k.org> (raw)
In-Reply-To: <20060105113708.GT27946@ftp.linux.org.uk>
Hi,
On Thursday 05 January 2006 12:37, Al Viro wrote:
> > OK. Nothing else depends on those; however, getuser.l stuff _is_
> > documented.
It actually was a nice feature and what I have seen so far look like bad
regression and makes the gas macros totally useless. Before it was possible
to define some pseudo assembly instructions, but if one can't pass some
simple address operand without quotes as an argument anymore...
> > Frankly, my preference long-term would be to kill the .macro and just
> > use C preprocessor for expansion. Do you have any objections against
> > such variant?
>
> Scratch that; too much PITA to implement the horrors you've got there
> (vararg recursive macros <shudder>).
Well, at that the time I wrote it, it very nicely cleaned up the old code
(which was even worse) and made additions very simple. The recursive macros
avoided a lot of simple typos. I'm not really happy that I have to change
that, it worked fine so far.
BTW I'm back in a few days and my online connectivity is rather limited right
now, so I hadn't really a good possibility to research the possible options
yet.
bye, Roman
prev parent reply other threads:[~2006-01-08 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 23:27 [PATCH 08/41] m68k: fix macro syntax to make current binutils happy Al Viro
2006-01-05 3:11 ` Roman Zippel
2006-01-05 3:51 ` Al Viro
2006-01-05 11:37 ` Al Viro
2006-01-08 17:11 ` Roman Zippel [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=200601081811.58669.zippel@linux-m68k.org \
--to=zippel@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=viro@ftp.linux.org.uk \
/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