Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753119Ab3GNTaE (ORCPT ); Sun, 14 Jul 2013 15:30:04 -0400 Received: from mail-wg0-f48.google.com ([74.125.82.48]:43253 "EHLO mail-wg0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753013Ab3GNTaD (ORCPT ); Sun, 14 Jul 2013 15:30:03 -0400 MIME-Version: 1.0 In-Reply-To: References: <1373806562-30422-1-git-send-email-artagnon@gmail.com> Date: Sun, 14 Jul 2013 19:30:00 +0000 Message-ID: Subject: Re: [LLVMdev] [PATCH] x86/asm: avoid mnemonics without type suffix From: Tim Northover To: Linus Torvalds Cc: Ramkumar Ramachandra , Jeremy Fitzhardinge , Andi Kleen , LKML , LLVMdev , Thomas Gleixner , Ingo Molnar Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 882 Lines: 29 > And that is why I think you should just consider "bt $x,y" to be > trivially the same thing and not at all ambiguous. Because there is > ABSOLUTELY ZERO ambiguity when people write > > bt $63, mem > > Zero. Nada. None. The semantics are *exactly* the same for btl and btq > in this case, so why would you want the user to specify one or the > other? I don't think you've actually tested that, have you? (x86-64) int main() { long val = 0xffffffff; char res; asm("btl $63, %1\n\tsetc %0" : "=r"(res) : "m"(val)); printf("%d\n", res); asm("btq $63, %1\n\tsetc %0" : "=r"(res) : "m"(val)); printf("%d\n", res); } Tim. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/