All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: kbuild-all@lists.01.org
Subject: Re: [peterz-queue:core/rcu 31/33] arch/x86/kernel/alternative.c:961:26: error: inlining failed in call to always_inline 'try_get_desc': function attribute mismatch
Date: Fri, 06 Mar 2020 10:51:27 +0100	[thread overview]
Message-ID: <20200306095127.GE3348@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <CACT4Y+Z=qy9MjhqOMNr2kYLwHy=gRXo0yqHBWBZpX2foRJBpMA@mail.gmail.com>

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

On Fri, Mar 06, 2020 at 06:34:49AM +0100, Dmitry Vyukov wrote:

> Say, consider, poke_int3_handler
> gets inlines in LTO build, and compiler says: you know what, I am just
> going to silently ignore your no_sanitize attribute to give you fun of
> re-debugging the issue you think you fixed ;)

*groan*, can't LTO still mess things up when combining translation units
build with different sanitize flags?

  reply	other threads:[~2020-03-06  9:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-29 14:37 [peterz-queue:core/rcu 31/33] arch/x86/kernel/alternative.c:961:26: error: inlining failed in call to always_inline 'try_get_desc': function attribute mismatch kbuild test robot
2020-03-05 13:43 ` Peter Zijlstra
2020-03-05 15:00   ` Dmitry Vyukov
2020-03-05 15:10     ` Dmitry Vyukov
2020-03-05 15:23       ` Dmitry Vyukov
2020-03-05 15:55         ` Peter Zijlstra
2020-03-05 16:29           ` Dmitry Vyukov
2020-03-05 18:47             ` Peter Zijlstra
2020-03-05 20:13               ` Dmitry Vyukov
2020-03-05 20:28                 ` Peter Zijlstra
2020-03-06  5:34                   ` Dmitry Vyukov
2020-03-06  9:51                     ` Peter Zijlstra [this message]
2020-03-06 10:06                       ` Dmitry Vyukov

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=20200306095127.GE3348@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.