public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/24760] -d option changes generated code Date: Wed, 09 Nov 2005 19:35:00 -0000 [thread overview] Message-ID: <20051109193501.4140.qmail@sourceware.org> (raw) In-Reply-To: <bug-24760-5394@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from amylaar at gcc dot gnu dot org 2005-11-09 19:35 ------- I have observed the -quiet influence only with a proprietary testcase so far (EEMBC aiifft01/bmark.c for sh-elf -m4 -ml -g -O3 -version -fomit-frame-pointer -funroll-loops --param max-inline-insns-single=50000). Compiling with -da -quiet generally makes this code smaller than compiling with -quiet only, but with a probability of about 1/5th -da -quiet produces larger code. -da without -quiet generally produces code that is larger than any of the above scenarios, but sometimes it produces identical code to -quiet (without -da). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24760
next prev parent reply other threads:[~2005-11-09 19:35 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-11-09 18:50 [Bug rtl-optimization/24760] New: " amylaar at gcc dot gnu dot org 2005-11-09 18:52 ` [Bug rtl-optimization/24760] " pinskia at gcc dot gnu dot org 2005-11-09 18:59 ` amylaar at gcc dot gnu dot org 2005-11-09 19:08 ` amylaar at gcc dot gnu dot org 2005-11-09 19:35 ` amylaar at gcc dot gnu dot org [this message] 2005-11-09 20:56 ` amylaar at gcc dot gnu dot org 2005-11-09 22:36 ` rakdver at gcc dot gnu dot org 2005-11-10 14:11 ` joern dot rennecke at st dot com 2005-11-10 14:17 ` pinskia at physics dot uc dot edu 2005-11-10 14:46 ` pinskia at gcc dot gnu dot org 2005-11-11 13:39 ` amylaar at gcc dot gnu dot org 2005-11-11 15:37 ` pinskia at gcc dot gnu dot org 2005-11-11 16:32 ` amylaar at gcc dot gnu dot org 2006-11-15 16:08 ` amylaar at gcc dot gnu dot org [not found] <bug-24760-4@http.gcc.gnu.org/bugzilla/> 2012-02-07 22:28 ` 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=20051109193501.4140.qmail@sourceware.org \ --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: linkBe 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).