From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: Ingo Molnar <mingo@elte.hu>,
heukelum@fastmail.fm, tglx@linutronix.de,
akpm@linux-foundation.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: gas 2.16 and assembly macros -- entry_64.S build failure
Date: Fri, 01 Oct 2010 10:21:48 -0700 [thread overview]
Message-ID: <4CA618AC.4000500@zytor.com> (raw)
In-Reply-To: <4CA61E8B020000780001A22A@vpn.id2.novell.com>
On 10/01/2010 08:46 AM, Jan Beulich wrote:
>
> Perhaps a misunderstanding? I meant to move the % back into
> movq_cfi's arguments, out of the macro body. pushq_cfi already
> is in the shape we need for having the option of using cpp macros
> when !CONFIG_AS_CFI.
>
Hm... I guess I'm not quite following. I don't really see how that
would help with movq_cfi, though?
>>> The other alternative, albeit disliked by Ingo, continues to be to use
>>> __stringify() on all non-trivial operands, which then wouldn't require
>>> suppressing CONFIG_AS_CFI for pre-2.17 binutils.
>>
>> You should be taken out and shot for even thinking that, never mind
>> putting it in writing...
>
> Thank you!
Just in case the intended sarcasm didn't read... I was of course joking,
although in all seriousness the __stringify() truly is
stick-your-eyes-out ugly and is just begging for future problems. It
really isn't an option.
-hpa
next prev parent reply other threads:[~2010-10-01 17:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 20:39 + arch-x86-kernel-entry_64s-fix-build-with-gas-2161.patch added to -mm tree akpm
[not found] ` <4C91F07E0200007800016B50@vpn.id2.novell.com>
[not found] ` <20100916082816.GA25681@elte.hu>
[not found] ` <4C91F3A30200007800016B64@vpn.id2.novell.com>
[not found] ` <20100916101355.GA31458@elte.hu>
[not found] ` <4C9219BC0200007800016C53@vpn.id2.novell.com>
2010-10-01 0:26 ` gas 2.16 and assembly macros -- entry_64.S build failure H. Peter Anvin
2010-10-01 1:01 ` Andrew Morton
2010-10-01 1:48 ` H. Peter Anvin
2010-10-01 8:27 ` Jan Beulich
2010-10-01 15:21 ` H. Peter Anvin
2010-10-01 15:46 ` Jan Beulich
2010-10-01 17:21 ` H. Peter Anvin [this message]
2010-10-04 7:36 ` Jan Beulich
2010-10-04 10:04 ` Avi Kivity
2010-10-04 15:43 ` H. Peter Anvin
2010-10-04 16:20 ` Avi Kivity
2010-10-04 18:23 ` H. Peter Anvin
2010-10-05 7:48 ` Avi Kivity
2010-10-05 7:51 ` Ingo Molnar
2010-10-05 9:09 ` Avi Kivity
2010-10-19 10:13 ` Jan Beulich
2010-10-19 10:32 ` Ingo Molnar
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=4CA618AC.4000500@zytor.com \
--to=hpa@zytor.com \
--cc=JBeulich@novell.com \
--cc=akpm@linux-foundation.org \
--cc=heukelum@fastmail.fm \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.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.