From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754144AbaACWek (ORCPT ); Fri, 3 Jan 2014 17:34:40 -0500 Received: from terminus.zytor.com ([198.137.202.10]:33612 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753385AbaACWej (ORCPT ); Fri, 3 Jan 2014 17:34:39 -0500 Message-ID: <52C73AD8.3080603@zytor.com> Date: Fri, 03 Jan 2014 14:34:00 -0800 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: David Woodhouse CC: mingo@kernel.org, tglx@linutronix.de, linux-kernel@vger.kernel.org Subject: Re: [PATCH] x86/boot: use .code16 instead of .code16gcc References: <1388788242.2391.75.camel@shinybook.infradead.org> In-Reply-To: <1388788242.2391.75.camel@shinybook.infradead.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/03/2014 02:30 PM, David Woodhouse wrote: > Since I just made .code16 work in LLVM, this removes one more barrier to > building the kernel with LLVM/clang. And it looks like 'clang -m16' for > the C code in arch/x86/boot shouldn't actually be that hard to do now > either. Nice. I would really like a gcc option "-m16" even if all it did was emit .code16gcc first in any assembly file (a bunch of the options we need for the 16-bit code is just so gcc doesn't emit code *before* the .code16gcc directive.) -hpa