public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "galtgendo at o2 dot pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/50506] gcc fails at assembly with -O1 while inlining is forced
Date: Sun, 25 Sep 2011 14:12:00 -0000	[thread overview]
Message-ID: <bug-50506-4-2kGB2ZEX0p@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50506-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Rafał Mużyło <galtgendo at o2 dot pl> 2011-09-25 13:51:14 UTC ---
So, I ran one more test:
gcc-4.6.1 -O2 -Wall -c -o fprintf-mini-bug-4.6.o fprintf-mini-bug-4.6.i
-fno-align-functions -fno-align-jumps -fno-align-labels -fno-align-loops
-fno-caller-saves -fno-crossjumping -fno-cse-follow-jumps -fno-devirtualize
-fno-expensive-optimizations -fno-gcse -fno-inline-small-functions -fno-ipa-cp
-fno-ipa-sra -fno-optimize-register-move -fno-optimize-sibling-calls
-fno-peephole2 -fno-regmove -fno-reorder-blocks -fno-reorder-functions
-fno-rerun-cse-after-loop -fno-schedule-insns2 -fno-strict-aliasing
-fno-thread-jumps -fno-tree-builtin-call-dce -fno-tree-pre
-fno-tree-switch-conversion -fno-tree-vrp

This makes '-Q --help=optimizers' output equal to '-O1' case, but
the testcase from comment 2 succeeds with this command.

So either '-Q --help=optimizers' output is incomplete or it's actually not any
specific option that triggers the change...
Well, unless there's a bug in the command line parser or a problem with the
specs.


  parent reply	other threads:[~2011-09-25 13:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-24 13:08 [Bug c/50506] New: " galtgendo at o2 dot pl
2011-09-24 13:18 ` [Bug c/50506] " galtgendo at o2 dot pl
2011-09-24 13:18 ` galtgendo at o2 dot pl
2011-09-24 13:46 ` galtgendo at o2 dot pl
2011-09-24 14:18 ` galtgendo at o2 dot pl
2011-09-24 16:05 ` pinskia at gcc dot gnu.org
2011-09-24 16:24 ` galtgendo at o2 dot pl
2011-09-25 12:27 ` rguenth at gcc dot gnu.org
2011-09-25 13:22 ` galtgendo at o2 dot pl
2011-09-25 13:58 ` galtgendo at o2 dot pl
2011-09-25 14:12 ` galtgendo at o2 dot pl [this message]
2011-09-25 17:20 ` rguenth at gcc dot gnu.org
2011-09-25 18:10 ` galtgendo at o2 dot pl

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-50506-4-2kGB2ZEX0p@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).