From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19902 invoked by alias); 15 Sep 2002 05:36:02 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 19887 invoked by uid 71); 15 Sep 2002 05:36:02 -0000 Date: Sat, 14 Sep 2002 22:36:00 -0000 Message-ID: <20020915053602.19886.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: "tprinceusa" Subject: Re: optimization/7909: ia64 warning 'Use of 'mov' may violate WAW dependency' on -O2 and above Reply-To: "tprinceusa" X-SW-Source: 2002-09/txt/msg00378.txt.bz2 List-Id: The following reply was made to PR optimization/7909; it has been noted by GNATS. From: "tprinceusa" To: , 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: To: 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