public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: linux-ia64@vger.kernel.org
Subject: Re: heads up: apparent GAS bug in current (CVS) binutils
Date: Fri, 13 May 2005 21:01:11 +0000	[thread overview]
Message-ID: <20050513210111.GB31069@lucon.org> (raw)
In-Reply-To: <200505122155.j4CLteGX024882@napali.hpl.hp.com>

On Fri, May 13, 2005 at 01:59:06PM -0700, David Mosberger wrote:
> >>>>> On Fri, 13 May 2005 13:50:04 -0700, "H. J. Lu" <hjl@lucon.org> said:
> 
>   HJ> On Fri, May 13, 2005 at 01:34:10PM -0700, David Mosberger wrote:
>   >> >>>>> On Fri, 13 May 2005 10:32:19 -0700, "Lu, Hongjiu"
>   >> <hongjiu.lu@intel.com> said:
> 
>   HJ> I tried binutils 2.15.92.0.2 20040927 and got the same
>   HJ> result. What is the version of assembler which you think is
>   HJ> good?
>   >>  The standard Debian/sarge as seems fine:
> 
>   >> $ as -v GNU assembler version 2.15 (ia64-linux) using BFD version
>   >> 2.15
> 
>   HJ> As I have mentioned before, it is an IPF specific kernel issue.
>   HJ> Basically, when you use weak functions, unwind info may be
>   HJ> wrong.  I am enclosing an updated kernel patch.
> 
> I agree that this is weird code that needs to be fixed, preferably by
> not using weak functions at all (as Andreas suggested).
> 
> However, there still seems to be a binutils issues here: if this is
> something binutils cannot properly support, it should issue an error,
> not silently generate wrong code, no?

I will see what I can do.


H.J.

  parent reply	other threads:[~2005-05-13 21:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-12 21:55 heads up: apparent GAS bug in current (CVS) binutils David Mosberger
2005-05-13 17:32 ` Lu, Hongjiu
2005-05-13 17:44 ` Lu, Hongjiu
2005-05-13 18:48 ` Lu, Hongjiu
2005-05-13 20:34 ` David Mosberger
2005-05-13 20:50 ` H. J. Lu
2005-05-13 20:59 ` David Mosberger
2005-05-13 21:01 ` H. J. Lu [this message]
2005-05-13 21:05 ` David Mosberger
2005-05-17 20:48 ` Luck, Tony
2005-05-17 20:53 ` 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=20050513210111.GB31069@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox