public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-51329-4-yCRlWypYOr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51329-4@http.gcc.gnu.org/bugzilla/>

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.


      parent reply	other threads:[~2011-11-28 18:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28  0:46 [Bug c++/51329] New: " andrew.mcpherson at gmail dot com
2011-11-28  1:12 ` [Bug c++/51329] " pinskia at gcc dot gnu.org
2011-11-28  7:51 ` andrew.mcpherson at gmail dot com
2011-11-28 11:33 ` manu at gcc dot gnu.org
2011-11-28 18:30 ` pinskia at gcc dot gnu.org [this message]

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=bug-51329-4-yCRlWypYOr@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).