linux-kernel - Re: inline asm semantics: output constraint width smaller than input

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <497A11F5.9090005@gmail.com>
Date:	Fri, 23 Jan 2009 20:52:37 +0200
From:	Török Edwin <edwintorok@...il.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	LLVM Developers Mailing List <llvmdev@...uiuc.edu>
Subject: Re: inline asm semantics: output constraint width smaller than input

On 2009-01-23 20:30, Ingo Molnar wrote:
> * Török Edwin <edwintorok@...il.com> wrote:
>
>   
>> Having said that, llvm-gcc is not yet able to compile the full Linux 
>> kernel on its own [for example the boot code, due to asm(".code16gcc")], 
>> but with LLVM 2.4 it was possible to build "arch=UM", and "arch=X86" (by 
>> using gcc to build the bootcode). I'd like LLVM 2.5 to be able to build 
>> the kernel, so I'll file bugs for llvm/kernel depending on where the 
>> problem is.
>>     
>
> Could we get LLVM folks on the Cc: and see how difficult it would be to 
> fix this on the LLVM side? Asm constraints are used all around the place 
> and different input/output types are very common.

I've added LLVMDev to Cc.
Your first post to the list may take a little longer to reach it (first
post is moderated by listmaster, no subscription required).

[For those who missed the initial conversation, see:
http://llvm.org/bugs/show_bug.cgi?id=3373#c9]

Best regards,
--Edwin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/