public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu 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 11:33:00 -0000	[thread overview]
Message-ID: <bug-51329-4-t1TCeHx167@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

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manu at gcc dot gnu.org

--- Comment #3 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2011-11-28 10:08:19 UTC ---
(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.

A better advice is to try to install a newer GCC on your own

http://gcc.gnu.org/install/

or using macports:

http://www.macports.org/install.php

I am sure you can find plenty of information on the net.

If the bug is still there, reopen this report.


  parent reply	other threads:[~2011-11-28 10:08 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 [this message]
2011-11-28 18:30 ` pinskia at gcc dot gnu.org

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-t1TCeHx167@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).