public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Török Edwin" <edwintorok@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>,
	David Howells <dhowells@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] __used is needed for function referenced only from inline asm
Date: Mon, 24 Nov 2008 11:50:44 +0200	[thread overview]
Message-ID: <492A78F4.9050007@gmail.com> (raw)
In-Reply-To: <20081124090403.GA25218@elte.hu>

On 2008-11-24 11:04, Ingo Molnar wrote:
> * Török Edwin <edwintorok@gmail.com> wrote:
>
>   
>> According to the gcc manual, the 'used' attribute should be applied to
>> functions referenced only from inline assembly.
>> This fixes a build failure with llvm-gcc-4.2, which deleted
>> __mutex_lock_slowpath, __mutex_unlock_slowpath.
>>
>> Signed-off-by: Török Edwin <edwintorok@gmail.com>
>> ---
>>  kernel/mutex.c |    8 ++++----
>>  1 files changed, 4 insertions(+), 4 deletions(-)
>>     
>
> quite sad - it's gcc inline assembly after all - applied to 
> tip/core/locking (for v2.6.29).

Thanks.

>  Should this get into v2.6.28 too?
>   

It is up to you to decide. I'd say it can't hurt to have it in 2.6.28,
and patch looks trivial enough.

On the other hand it is not urgent either, building a full x86 kernel
with llvm-gcc only still has some loose ends
(there is something wrong with the boot code for example, like it can't
detect vga modes, I didn't figure out what is wrong yet)

Best regards,
--Edwin

      reply	other threads:[~2008-11-24  9:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-24  8:17 [PATCH] __used is needed for function referenced only from inline asm Török Edwin
2008-11-24  8:57 ` Geert Uytterhoeven
2008-11-24  9:22   ` Andi Kleen
2008-11-24  9:32     ` Andreas Schwab
2008-11-24  9:53       ` Andi Kleen
2008-11-24  9:04 ` Ingo Molnar
2008-11-24  9:50   ` Török Edwin [this message]

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=492A78F4.9050007@gmail.com \
    --to=edwintorok@gmail.com \
    --cc=arjan@linux.intel.com \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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