public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "tprinceusa" <tprinceusa@netzero.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/7909: ia64 warning 'Use of 'mov' may violate WAW dependency' on -O2 and above
Date: Sat, 14 Sep 2002 22:36:00 -0000	[thread overview]
Message-ID: <20020915053602.19886.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/7909; it has been noted by GNATS.

From: "tprinceusa" <tprinceusa@netzero.net>
To: <ben@zeus.com>,
	<gcc-gnats@gcc.gnu.org>
Cc:  
Subject: Re: optimization/7909: ia64 warning 'Use of 'mov' may violate WAW dependency' on -O2 and above
Date: Sat, 14 Sep 2002 22:27:18 -0700

 ----- Original Message -----
 From: <ben@zeus.com>
 To: <gcc-gnats@gcc.gnu.org>
 Sent: Friday, September 13, 2002 6:38 AM
 Subject: optimization/7909: ia64 warning 'Use of 'mov' may violate WAW dependency' on -O2 and above
 
 
 >
 > >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
 I see such messages reported consistently in gcc testsuite, for fp-cmp5.  In some cases, including this, the compiled code runs OK.
 It is possible to provoke many more such problems, e.g. by use of -frename-registers -O2, some of which do involve broken code
 generation.  Do others simply suppress these warnings?
 
 
 
 
 
 
 -------------------------------------------
 Introducing NetZero Long Distance
 Unlimited Long Distance only $29.95/ month!
 Sign Up Today! www.netzerolongdistance.com


             reply	other threads:[~2002-09-15  5:36 UTC|newest]

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

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=20020915053602.19886.qmail@sources.redhat.com \
    --to=tprinceusa@netzero.net \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).