public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "m101010a at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55319] Using -fwhole-program inhibits optimization
Date: Sun, 18 Nov 2012 22:13:00 -0000	[thread overview]
Message-ID: <bug-55319-4-vXIeeOpQJK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55319-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #2 from m101010a at gmail dot com 2012-11-18 22:13:23 UTC ---
Actually, it does depend on IO; the optimizations aren't performed in either
case if I declare but don't define putchar, and if do something simple like
assigning to a volatile int in putchar then the optimizations are performed in
both cases.  If I assert(false) in putchar, gcc optimizes the fwhole-program
version to a failed assert, but doesn't without fwhole-program, which is the
opposite of what it does with IO.


  parent reply	other threads:[~2012-11-18 22:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14  4:48 [Bug c++/55319] New: " m101010a at gmail dot com
2012-11-18 14:01 ` [Bug c++/55319] " paolo.carlini at oracle dot com
2012-11-18 22:13 ` m101010a at gmail dot com [this message]
2012-11-19  0:16 ` paolo.carlini at oracle dot com

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-55319-4-vXIeeOpQJK@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).