public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ben@zeus.com
To: gcc-gnats@gcc.gnu.org
Subject: optimization/7909: ia64 warning 'Use of 'mov' may violate WAW dependency' on -O2 and above
Date: Fri, 13 Sep 2002 06:46:00 -0000	[thread overview]
Message-ID: <20020913133845.16201.qmail@sources.redhat.com> (raw)


>Number:         7909
>Category:       optimization
>Synopsis:       ia64 warning 'Use of 'mov' may violate WAW dependency' on -O2 and above
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Sep 13 06:46:02 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Ben
>Release:        3.2
>Organization:
>Environment:
Compiling native code for a ia64 box
>Description:
The code sample is a fairly ugly routine to convert pointers
into a hex string. The code compiles fine with all levels of
optimisation. However, with -O2 and above, gcc reports the
following warning messages:

/tmp/cc2HCufe.s: Assembler messages:
/tmp/cc2HCufe.s:133: Warning: Use of 'mov' may violate WAW dependency 'GR%, % in 1 - 127' (impliedf), specific resource number is 14
/tmp/cc2HCufe.s:133: Warning: Only the first path encountering the conflict is reported
>How-To-Repeat:
Compile the code with -O2 or above. No other compile flags required.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/x-csrc; name="gccia64.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="gccia64.c"

I2luY2x1ZGUgPHN0ZGlvLmg+CgpzdGF0aWMgCmNvbnN0IHVuc2lnbmVkIGNoYXIgbjJ4WzE2XSA9
IHsgJzAnLCAnMScsICcyJywgJzMnLCAnNCcsICc1JywgJzYnLCAnNycsCiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgJzgnLCAnOScsICdhJywgJ2InLCAnYycsICdkJywgJ2UnLCAnZicg
fTsKCgppbnQKbWFpbiggaW50IGFyZ2MsIGNoYXIgKiphcmd2ICkKewogICBjaGFyIGJ1ZmZbIDI1
NiBdOwogICBjaGFyICpxID0gYnVmZjsKCiAgIHZvaWQgKnB0ciA9ICh2b2lkICopIDB4MDEyMzQ1
Njc7CiAgIGNvbnN0IHVuc2lnbmVkIGNoYXIgKm51bSA9ICh1bnNpZ25lZCBjaGFyICopICZwdHI7
CiAgIGNvbnN0IHVuc2lnbmVkIGNoYXIgKnRvcCA9IG51bSArIHNpemVvZiggdm9pZCAqICk7CiAg
IAogICAqcSsrID0gJzAnOwogICAqcSsrID0gJ3gnOwoKICAgaWYoIHB0ciA9PSAwICkgKnErKyA9
ICcwJzsKICAgZWxzZSB3aGlsZSggbnVtICE9IHRvcCApIHsKICAgICAgY29uc3QgaW50IGJ5dGUg
PSAqLS10b3A7CiAgICAgIGNvbnN0IGludCB1cHBlcm5pYmJsZSA9IChieXRlICYgMHhmMCkgPj4g
NDsKICAgICAgaWYoIHEgIT0gYnVmZisyIHx8IHVwcGVybmliYmxlICkgKnErKyA9IG4yeFsgdXBw
ZXJuaWJibGUgXTsKICAgICAgY29uc3QgaW50IGxvd2VybmliYmxlID0gYnl0ZSAmIDB4ZjsKICAg
ICAgaWYoIHEgIT0gYnVmZisyIHx8IGxvd2VybmliYmxlICkgKnErKyA9IG4yeFsgbG93ZXJuaWJi
bGUgXTsKICAgfQoKICAgKnErKyA9ICdcMCc7CiAgIHByaW50ZiggIiVzXG4iLCBidWZmICk7Cn0K


             reply	other threads:[~2002-09-13 13:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-13  6:46 ben [this message]
2002-09-14 22:36 tprinceusa
2002-10-06 19:46 rth

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=20020913133845.16201.qmail@sources.redhat.com \
    --to=ben@zeus.com \
    --cc=gcc-gnats@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).