From: Ian Lance Taylor <iant@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Arnaud Lacombe <lacombar@gmail.com>,
gcc-help@gcc.gnu.org, stufever@gmail.com,
linux-kernel@vger.kernel.org,
Wang Shaoyan <wangshaoyan.pt@taobao.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] TRACING: Fix a copmile warning
Date: Mon, 25 Jul 2011 22:55:52 -0700 [thread overview]
Message-ID: <mcrtya9mvpz.fsf@coign.corp.google.com> (raw)
In-Reply-To: <1311642628.3526.58.camel@gandalf.stny.rr.com> (Steven Rostedt's message of "Mon, 25 Jul 2011 21:10:28 -0400")
Steven Rostedt <rostedt@goodmis.org> writes:
> Compiling with -O2 (which gives no warning) (x86_64) produces:
>
> 0000000000000000 <fn>:
> 0: 48 83 ec 08 sub $0x8,%rsp
> 4: e8 00 00 00 00 callq 9 <fn+0x9>
> 5: R_X86_64_PC32 e-0x4
> 9: 48 85 c0 test %rax,%rax
> c: 74 1a je 28 <fn+0x28>
> e: e8 00 00 00 00 callq 13 <fn+0x13>
> f: R_X86_64_PC32 f-0x4
> 13: 48 85 c0 test %rax,%rax
> 16: 74 10 je 28 <fn+0x28>
> 18: 48 83 c4 08 add $0x8,%rsp
> 1c: e9 00 00 00 00 jmpq 21 <fn+0x21>
> 1d: R_X86_64_PC32 g-0x4
> 21: 0f 1f 80 00 00 00 00 nopl 0x0(%rax)
> 28: 48 83 c4 08 add $0x8,%rsp
> 2c: c3 retq
>
> and compiling with -Os:
>
> 0000000000000000 <fn>:
> 0: 55 push %rbp
> 1: 53 push %rbx
> 2: 51 push %rcx
> 3: e8 00 00 00 00 callq 8 <fn+0x8>
> 4: R_X86_64_PC32 e-0x4
> 8: 48 85 c0 test %rax,%rax
> b: 48 89 c3 mov %rax,%rbx
> e: 74 08 je 18 <fn+0x18>
> 10: e8 00 00 00 00 callq 15 <fn+0x15>
> 11: R_X86_64_PC32 f-0x4
> 15: 48 89 c5 mov %rax,%rbp
> 18: 48 85 ed test %rbp,%rbp
> 1b: 74 0d je 2a <fn+0x2a>
> 1d: 48 85 db test %rbx,%rbx
> 20: 74 08 je 2a <fn+0x2a>
> 22: 5a pop %rdx
> 23: 5b pop %rbx
> 24: 5d pop %rbp
> 25: e9 00 00 00 00 jmpq 2a <fn+0x2a>
> 26: R_X86_64_PC32 g-0x4
> 2a: 58 pop %rax
> 2b: 5b pop %rbx
> 2c: 5d pop %rbp
> 2d: c3 retq
>
> Which is 1 byte more than -O2. I would think that -Os would be smaller.
Ideally, it should be, yes. The -Os code would be smaller except that
it needs to save a register across a function call, which forces it to
push and pop %rbx, which in turn means that stack alignment adds yet
another push and two pop instructions. It's a heuristic failure.
Ian
next prev parent reply other threads:[~2011-07-26 5:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 9:40 [PATCH] TRACING: Fix a copmile warning stufever
2011-07-25 18:32 ` Steven Rostedt
2011-07-25 19:43 ` Arnaud Lacombe
2011-07-25 20:19 ` Steven Rostedt
2011-07-25 20:28 ` Arnaud Lacombe
2011-07-25 22:38 ` Arnaud Lacombe
2011-07-25 23:49 ` Steven Rostedt
2011-07-25 23:52 ` Arnaud Lacombe
2011-07-26 0:14 ` Steven Rostedt
2011-07-25 23:50 ` Arnaud Lacombe
2011-07-25 23:58 ` Arnaud Lacombe
2011-07-26 0:08 ` Steven Rostedt
2011-07-26 0:35 ` Steven Rostedt
2011-07-26 0:44 ` Ian Lance Taylor
2011-07-26 0:41 ` Ian Lance Taylor
2011-07-26 1:08 ` Arnaud Lacombe
2011-07-26 1:12 ` Steven Rostedt
2011-07-26 1:19 ` Arnaud Lacombe
2011-07-26 20:43 ` Jeff Law
2011-07-26 1:10 ` Steven Rostedt
2011-07-26 5:55 ` Ian Lance Taylor [this message]
2011-07-26 12:00 ` Paulo Marques
2011-07-26 13:18 ` Jesper Juhl
2011-07-26 13:32 ` Paulo Marques
2011-07-26 13:55 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2011-07-18 9:35 stufever
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=mcrtya9mvpz.fsf@coign.corp.google.com \
--to=iant@google.com \
--cc=fweisbec@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=lacombar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=stufever@gmail.com \
--cc=wangshaoyan.pt@taobao.com \
/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