public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: aj@suse.de
To: gcc-gnats@gcc.gnu.org
Subject: c/7257: -O3 -fverbose-asm does not display -flag-inline-functions
Date: Wed, 10 Jul 2002 00:26:00 -0000 [thread overview]
Message-ID: <20020710071828.3408.qmail@sources.redhat.com> (raw)
>Number: 7257
>Category: c
>Synopsis: -O3 -fverbose-asm does not display -flag-inline-functions
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Jul 10 00:26:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: aj@suse.de
>Release: GCC 3.1 CVS, GCC 3.2 CVS
>Organization:
>Environment:
i686-linux-gnu
>Description:
According to the manual, -O3 enables -finline-functions.
-fverbose-asm enables the output of all flags that are set.
Some analysis:
- toplev.c sets flag_inline_functions
- c-common.c sets then in c_common_post_options flag_inline_functions to 0 and sets flag_inline_trees to 2.
- print_switch_values in toplev.c sees now
flag_inline_functions=0 but does not see flag_inline_trees and therefore the flag is not shown.
The same happens for C++ in cp/decl.c.
This is a regression from GCC 2.95.3.
>How-To-Repeat:
gcc -O3 -fverbose-asm -save-temps hello.c
outputs a hello.s with:
GNU C version 3.2 20020707 (experimental) (i686-pc-linux-gnu)
# compiled by GNU C version 3.2 20020707 (experimental).
# options passed: -fpreprocessed -O3 -fverbose-asm
# options enabled: -fdefer-pop -foptimize-sibling-calls -fcse-follow-jumps
# -fcse-skip-blocks -fexpensive-optimizations -fthread-jumps
# -fstrength-reduce -fpeephole -fforce-mem -ffunction-cse
# -fkeep-static-consts -fcaller-saves -fpcc-struct-return -fgcse -fgcse-lm
# -fgcse-sm -floop-optimize -fcrossjumping -fif-conversion -fif-conversion2
# -frerun-cse-after-loop -frerun-loop-opt -fdelete-null-pointer-checks
# -fschedule-insns2 -fsched-interblock -fsched-spec -fbranch-count-reg
# -freorder-blocks -freorder-functions -frename-registers -fcprop-registers
# -fcommon -fverbose-asm -fgnu-linker -fregmove -foptimize-register-move
# -fargument-alias -fstrict-aliasing -fmerge-constants
# -fzero-initialized-in-bss -fident -fpeephole2 -fguess-branch-probability
# -fmath-errno -ftrapping-math -m80387 -mhard-float -mno-soft-float
# -mieee-fp -mfp-ret-in-387 -mcpu=pentiumpro -march=i386
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
reply other threads:[~2002-07-10 7:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020710071828.3408.qmail@sources.redhat.com \
--to=aj@suse.de \
--cc=gcc-gnats@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).