From: "H. J. Lu" <hjl@lucon.org>
To: linux-ia64@vger.kernel.org
Subject: Re: WAW dependency messages
Date: Wed, 15 Oct 2003 23:51:44 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106626192222924@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106625678318659@msgid-missing>
On Wed, Oct 15, 2003 at 04:14:16PM -0700, Jesse Barnes wrote:
> On Wed, Oct 15, 2003 at 03:53:35PM -0700, H. J. Lu wrote:
> > On Wed, Oct 15, 2003 at 03:24:34PM -0700, Jesse Barnes wrote:
> > > In case anyone's interested, I just found a gcc bugzilla bug for the
> > > dependency violation stuff that always gets printed when we compile the
> > > kernel. I've added some information to it. The bug number is 12287,
> > > and you can see the whole thing at
> > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id\x12287.
> > >
> >
> > I am working on some DV problems in assembler. With the new assembler,
> > there are fewer DV warnings when compiling 2.4.21 kernel. If someone
> > sends me small asm testcases, I will look into them.
>
> There's a testcase in the bug, but what prompted me to look was all of
That testcase should be fixed in the next binutils.
> the messages that get printed out when compiling a 2.6 kernel. Does
Kernel is a totally different issue. You can send me small asm
testcases. I will see what I can do.
> binutils 2.14.90.0.6 contain the fixes you're talking about? That's
> what I'm using...
>
I am working on 2.14.90.0.7 which should have the fix.
H.J.
next prev parent reply other threads:[~2003-10-15 23:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 22:24 WAW dependency messages Jesse Barnes
2003-10-15 22:53 ` H. J. Lu
2003-10-15 23:14 ` Jesse Barnes
2003-10-15 23:51 ` H. J. Lu [this message]
2003-10-15 23:56 ` Jesse Barnes
2003-10-16 1:34 ` Chen, Kenneth W
2003-10-16 1:49 ` David Mosberger
2003-10-20 22:24 ` Jim Wilson
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-106626192222924@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