From: Jim Wilson <wilson@specifixinc.com>
To: linux-ia64@vger.kernel.org
Subject: RE: WAW dependency messages
Date: Mon, 20 Oct 2003 22:24:12 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106668880406921@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106625678318659@msgid-missing>
On Wed, 2003-10-15 at 18:34, Chen, Kenneth W wrote:
> Oddly enough, "as test.S" doesn't have warning message, but "as -x
> test.S" does. gcc is execve with "as -x" which triggers the warning
> message.
GNU as only does DV checking if the -x option is specified.
The DV checking stuff was never properly finished. It should be enabled
by default. And we should emit errors instead of warnings for provable
DVs. However, if we did that, we would then have the problem that false
positives from bugs would prevent the compiler from working. So we
would have to add an option to disable DV checking and have the compiler
emit it. But then we would have the problem that the compiler output
would not get any DV checking from the assembler, which is a worse
problem than what we have now. We really need to get the bugs fixed
first, and then emit errors by default for DVs. I'm glad to see that HJ
has time to work on these problems.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
prev parent reply other threads:[~2003-10-20 22:24 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
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 [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-106668880406921@msgid-missing \
--to=wilson@specifixinc.com \
--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