From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2929 invoked by alias); 23 Sep 2011 17:38:40 -0000 Received: (qmail 2810 invoked by uid 22791); 23 Sep 2011 17:38:38 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 23 Sep 2011 17:38:25 +0000 From: "gary at intrepid dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/50489] [UPC/IA64] mis-schedule of MEM ref with -ftree-vectorize and -fschedule-insns2 Date: Fri, 23 Sep 2011 17:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gary at intrepid dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-09/txt/msg01692.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50489 --- Comment #4 from Gary Funck 2011-09-23 17:38:18 UTC --- (In reply to comment #3) > Does the problem vanish if you add -fno-strict-aliasing? > > One more thing, you mention -O2 in the flags, but then refer to selective > scheduler, which is only enabled at -O3. Perhaps you meant Haifa scheduler. The tests still fail with "-O3 -fno-strict-aliasing". They pass with "-O3 -fno-schedule-insns2". We mentioned -O2 in the bug report, because it helped rule out other optimizations that -O3 might imply. Then we selectively added "-ftree-vectorize" and "-fschedule-insns2" to demonstrate that the combination of those additional optimizations will demonstrate the mis-scheduling. If there are additional tests that you suggest that we can run to help narrow this down, let us know, and we'll try to provide that additional information. Also, we can provide a script to run gdb on "cc1upc", if that helps. Thanks.