public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Adrian Bunk <bunk@kernel.org>, Jie Zhang <jzhang.linux@gmail.com>,
	bryan.wu@analog.com, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] blackfin: "extern inline" -> "static inline"
Date: Thu, 25 Oct 2007 13:28:04 -0700	[thread overview]
Message-ID: <4720FC54.1020705@zytor.com> (raw)
In-Reply-To: <8bd0f97a0710251320m3490c53dpe85656a939e8536e@mail.gmail.com>

Mike Frysinger wrote:
>> Do you have any example for your claim "to get gcc to not inline things
>> when building debug versions"?
> 
> $ cat test.c
> __attribute__((always_inline)) int foo(void) { return 0; }
> int main(void){ return foo(); }
> $ gcc -g test.c -o test
> $ readelf -s test | grep FUNC | grep -v _
>     61: 00000000004004b8    11 FUNC    GLOBAL DEFAULT   13 foo
>     68: 00000000004004c3    11 FUNC    GLOBAL DEFAULT   13 main
> 
> looks pretty straightforward to me
> -mike

For "debug version" meaning -O0, this is true.

	-hpa

  reply	other threads:[~2007-10-25 20:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 16:26 [2.6 patch] blackfin: "extern inline" -> "static inline" Adrian Bunk
2007-10-25  2:47 ` Jie Zhang
2007-10-25  3:00   ` Mike Frysinger
2007-10-25  3:06     ` H. Peter Anvin
2007-10-25  3:17       ` Mike Frysinger
2007-10-25 15:05       ` Adrian Bunk
2007-10-25 16:16         ` Mike Frysinger
2007-10-25 16:53           ` Adrian Bunk
2007-10-25 20:07             ` Mike Frysinger
2007-10-25 20:18               ` Adrian Bunk
2007-10-25 20:20                 ` Mike Frysinger
2007-10-25 20:28                   ` H. Peter Anvin [this message]
2007-10-25 20:45                     ` Mike Frysinger
2007-10-25 20:53                       ` H. Peter Anvin
2007-10-25 20:47                     ` Adrian Bunk
2007-10-25 20:54                       ` H. Peter Anvin
2007-10-25 20:46                   ` Adrian Bunk

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=4720FC54.1020705@zytor.com \
    --to=hpa@zytor.com \
    --cc=bryan.wu@analog.com \
    --cc=bunk@kernel.org \
    --cc=jzhang.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vapier.adi@gmail.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