public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Hui Zhu <teawater@gmail.com>,
	linux-kernel@vger.kernel.org, gdb@sourceware.org,
	hellogcc@freelists.org
Subject: Re: [PATCH] Built kernel without -O2 option
Date: Mon, 29 Nov 2010 13:03:42 -0500	[thread overview]
Message-ID: <13378.1291053822@localhost> (raw)
In-Reply-To: Your message of "Mon, 29 Nov 2010 16:52:50 +0800." <20101129085250.GF5218@cr0.nay.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 621 bytes --]

On Mon, 29 Nov 2010 16:52:50 +0800, Américo Wang said:

> >For example:
> >ifdef CONFIG_CC_CLOSE_OPTIMIZATION
> >CFLAGS_fpu.o                           += -O2
> >CFLAGS_aesni-intel_glue.o              += -O2
> >CFLAGS_ghash-clmulni-intel_glue.o      += -O2
> >endif
> 
> No, I didn't mean this, I meant some function that have to be inlined
> are those who only work when being inlined, e.g. current_text_addr().
> 
> I think it is not alone. :)

Anything that uses the gcc __builtin_return_adress() extension should also be
audited - that returns different results for inlined and non-inlined callers.


[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2010-11-29 18:05 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-29  3:56 [PATCH] Built kernel without -O2 option Hui Zhu
2010-11-29  8:16 ` Américo Wang
2010-11-29  8:18   ` microcai
2010-11-29  8:24   ` Hui Zhu
     [not found]     ` <4CF36741.9000808@loongson.cn>
2010-11-29  8:47       ` [hellogcc] " Hui Zhu
2010-11-29  8:55         ` Steven
2010-11-29  8:57           ` Hui Zhu
2010-11-29  9:45         ` 乔崇
2010-11-29 18:10           ` Valdis.Kletnieks
2010-11-29 18:34             ` Steven J. Magnani
2010-11-29 22:03             ` Alexey Dobriyan
2010-12-01 13:21               ` Hui Zhu
2010-12-01 12:23           ` bekars
2010-12-01 13:24             ` Hui Zhu
2010-12-01 13:58               ` bekars
2010-12-01 15:01                 ` Hui Zhu
2010-12-01 15:42                   ` jovi zhang
2010-11-29  8:52     ` Américo Wang
2010-11-29  9:11       ` Hui Zhu
2010-11-29 18:03       ` Valdis.Kletnieks [this message]
2010-11-29 20:51       ` richard -rw- weinberger
2010-11-29 21:00         ` Arnaud Lacombe
2010-11-29 21:07           ` richard -rw- weinberger
2010-11-29  9:44   ` Christian Borntraeger
2010-11-29 11:12     ` Segher Boessenkool
2010-11-29 11:17       ` Christian Borntraeger
2010-11-29 11:57         ` Nicholas Mc Guire
2010-12-01 12:18     ` Hui Zhu
2010-11-29  9:59 ` Andi Kleen
2010-11-29 10:12   ` Mark Wielaard
2010-11-30  9:31     ` Américo Wang
2010-11-30 18:40       ` Michael Snyder
2010-12-01 12:52   ` Hui Zhu
2010-11-29 19:05 ` Jan Kratochvil
2010-11-29 21:07 ` Arnaud Lacombe
2010-11-30 22:40   ` Petr Hluzín
2010-12-01 13:42     ` Hui Zhu
2010-12-01 13:10   ` Hui Zhu
2011-01-24  7:47 ` Hui Zhu
2011-01-24  8:11   ` Kevin Pouget
2011-01-24 12:42     ` Hui Zhu
2011-01-28  3:41       ` Hui Zhu
2011-02-17  2:43         ` Hui Zhu
     [not found]           ` <AANLkTik+beFdZZHLyei044q8EPHwvmiKoFAvAHsNuhmw@mail.gmail.com>
2011-02-21 12:51             ` Kevin Pouget
2011-02-23  5:19             ` Hui Zhu

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=13378.1291053822@localhost \
    --to=valdis.kletnieks@vt.edu \
    --cc=gdb@sourceware.org \
    --cc=hellogcc@freelists.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=teawater@gmail.com \
    --cc=xiyou.wangcong@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