mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Meyer <thomas@m3y3r.de>
To: Valdis.Kletnieks@vt.edu
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [UML] 3.16 build without optimization fails
Date: Tue, 19 Aug 2014 22:19:58 +0200	[thread overview]
Message-ID: <E1XJpsx-0001oD-AE@www17.your-server.de> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 951 bytes --]

Hi.

Thanks for your answer.

There goes my plan to better understand an UML kernel lock up by using a debugger... Everything gets optimised out with -O2 :-(

Can you give an example function that relies on this GCC feature?

With kind regards
Thomas

Am 19.08.2014 22:06 schrieb Valdis.Kletnieks@vt.edu:
>
> On Tue, 19 Aug 2014 21:12:10 +0200, Thomas Meyer said: 
> > > Hi, 
> > > 
> > > the build with -O0 fails with: 
>
> > > bug or feature? 
> > > 
> > > any ideas? 
>
> Feature.  The kernel is *known* to not build with -O0, because that 
> disables *all* function inlining, and there's several functions that *have* 
> to be inlined in order to function properly (most notably, anything 
> that uses the gcc __builtin_return_address in a function that is expected 
> to be inlined). 
ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

             reply	other threads:[~2014-08-19 20:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 20:19 Thomas Meyer [this message]
2014-08-19 20:25 ` Valdis.Kletnieks
2014-08-19 20:26 ` Richard Weinberger
  -- strict thread matches above, loose matches on Subject: below --
2014-08-19 20:35 Thomas Meyer
2014-08-19 19:12 Thomas Meyer
2014-08-19 20:06 ` Valdis.Kletnieks

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=E1XJpsx-0001oD-AE@www17.your-server.de \
    --to=thomas@m3y3r.de \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®