From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-375189-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 27466 invoked by alias); 28 Nov 2011 18:23:28 -0000
Received: (qmail 27448 invoked by uid 22791); 28 Nov 2011 18:23:26 -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; Mon, 28 Nov 2011 18:23:12 +0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51329] O3 optimizes away a loop
Date: Mon, 28 Nov 2011 18:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-51329-4-yCRlWypYOr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51329-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51329-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2011-11/txt/msg02685.txt.bz2

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51329

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-11-28 18:23:05 UTC ---
(In reply to comment #3)
> (In reply to comment #2)
> > Thanks, will report to apple.
> 
> Reporting to Apple is useless, they have long moved to Clang, so they won't fix
> bugs in GCC. By extension, advising someone to report GCC bugs to Apple is
> doubly-useless. You are basically telling them "Forget about GCC, use Clang!"
> because this is what Apple will tell them.
> 

Actually this is incorrect because Apple needs to know that a lot of folks
still use GCC and want to use GCC but that is all offtopic here really.  The
thing is that Apple supplied the GCC they are using and it is heavily modified
so Apple needs to support what they provided.