All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: WAW dependency messages
Date: Thu, 16 Oct 2003 01:34:41 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106626810627108@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106625678318659@msgid-missing>

> Kernel is a totally different issue. You can send me small asm
> testcases. I will see what I can do.

Something as simple as:

        itc.i r18
        ;;
        ld8 r19=[r17]

Will generate
aa.S: Assembler messages:
aa.S:3: Warning: Use of 'ld8' violates RAW dependency 'DTC' (data)
aa.S:1: Warning: This is the location of the conflicting usage

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.

- Ken

  parent reply	other threads:[~2003-10-16  1:34 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 [this message]
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-106626810627108@msgid-missing \
    --to=kenneth.w.chen@intel.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 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.