From: "H. J. Lu" <hjl@lucon.org>
To: linux-ia64@vger.kernel.org
Subject: Re: binutils 2.14.90.7 DV warnings
Date: Wed, 05 Nov 2003 18:57:25 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106805896119914@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106805289711668@msgid-missing>
On Wed, Nov 05, 2003 at 09:20:20AM -0800, Jesse Barnes wrote:
> I just tried out the latest versions of gcc (3.3.2) and binutils
> (2.14.90.7) to see if the dependency violation stuff had been fixed
> since I saw that the bintutils changelog mentioned it, but unfortunately
> I still see some warnings (though I _think_ there are fewer than
> before). I've attached the kernel config I used to build
> linux-2.6.0-test9-mm2, but it should also work with David or Linus's BK
> trees.
There are still a few false warnings on kernel assembly codes. I tried
some of them on Intel IPF assembler and IAS didn't warn them at all
even if DV does exist. I looked at the assembler source. It cann't
be fixed without changing DV check infrastructure. I will look into
them when I find time.
H.J.
prev parent reply other threads:[~2003-11-05 18:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 17:20 binutils 2.14.90.7 DV warnings Jesse Barnes
2003-11-05 18:57 ` H. J. Lu [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=marc-linux-ia64-106805896119914@msgid-missing \
--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