From: Thomas Meyer <thomas@m3y3r.de>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: linux@thorsten-knabe.de,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
Subject: Re: [UML] 3.16 build without optimization fails
Date: Tue, 19 Aug 2014 22:35:15 +0200 [thread overview]
Message-ID: <E1XJq7k-0002hd-8o@www17.your-server.de> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1418 bytes --]
Yes, it's still there.
Am 19.08.2014 22:26 schrieb Richard Weinberger <richard.weinberger@gmail.com>:
>
> On Tue, Aug 19, 2014 at 10:19 PM, Thomas Meyer <thomas@m3y3r.de> wrote:
> > 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 :-(
>
> Is it the filesystem/block lockup you saw some time ago?
> Maybe Thorsten can give more details.
> He sent me an patch off list a few days ago.
>
> > 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).
>
>
>
> --
> Thanks,
> //richard
ÿôèº{.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¥
next reply other threads:[~2014-08-19 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 20:35 Thomas Meyer [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-19 20:19 Thomas Meyer
2014-08-19 20:25 ` Valdis.Kletnieks
2014-08-19 20:26 ` Richard Weinberger
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=E1XJq7k-0002hd-8o@www17.your-server.de \
--to=thomas@m3y3r.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@thorsten-knabe.de \
--cc=richard.weinberger@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
all inboxes | Powered by JetHome®