From: "H. J. Lu" <hjl@lucon.org>
To: linux-ia64@vger.kernel.org
Subject: Re: PATCH: Fix 2.6 kernel ia64 directives
Date: Wed, 09 Feb 2005 20:05:47 +0000 [thread overview]
Message-ID: <20050209200547.GA31021@lucon.org> (raw)
In-Reply-To: <20050202221918.GA7973@lucon.org>
On Wed, Feb 09, 2005 at 11:35:32AM -0800, David Mosberger wrote:
> >>>>> On Mon, 07 Feb 2005 12:11:48 -0800, James E Wilson <wilson@tuliptree.org> said:
>
> >> "The assembler ignores the name operands of the
> >> directive."
>
> Jim> I'd call this is a bug in the manual.
>
> Perhaps.
>
> Jim> Also, I'm told that current IAS gives an error in this case, which is
> Jim> why gas was modified to do likewise. Unfortunately, I don't have access
> Jim> to IAS, or to the HP assembler, so I can not check that. If this is
> Jim> wrong, then changing it to a warning certainly makes sense.
>
> Why should it depend on IAS as to whether GAS does or does not produce
> an error? The fact is that GAS has _not_ in the past issued an error
FYI, I checked the current IAS, the name after endp IS ignored by IAS.
> and it's not acceptable to break existing code for no good reason.
> Making it a warning is fine, of course. That will alert people to the
> fact that they may have an unintentional inconsistency in their code
> and will let them fix the error at their convenience. After enough
> time has elapsed (at least a year), the severity could (and probably
> should) be raised to an error.
>
I guess Jim is still catching his emails. I will give him a few days
to go though my ia64 gas patches which deal this very issues.
H.J.
next prev parent reply other threads:[~2005-02-09 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 22:19 PATCH: Fix 2.6 kernel ia64 directives H. J. Lu
2005-02-02 22:50 ` David Mosberger
2005-02-03 8:12 ` Jan Beulich
2005-02-07 20:11 ` James E Wilson
2005-02-07 22:18 ` James E Wilson
2005-02-09 19:35 ` David Mosberger
2005-02-09 20:05 ` H. J. Lu [this message]
2005-02-09 20:10 ` James E Wilson
2005-02-09 21:11 ` David Mosberger
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=20050209200547.GA31021@lucon.org \
--to=hjl@lucon.org \
--cc=linux-ia64@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.