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] [day] [month] [year] [list]
Message-ID: <4980C73D.9010809@zytor.com>
Date:	Wed, 28 Jan 2009 12:59:41 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Kyle Moffett <kyle@...fetthome.net>
CC:	Duncan Sands <baldrick@...e.fr>, llvmdev@...uiuc.edu,
	Ingo Molnar <mingo@...e.hu>,
	Török Edwin <edwintorok@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [LLVMdev] inline asm semantics: output constraint width smaller
 	than input

Kyle Moffett wrote:
> 
> On a BE 32-bit machine, the "output register" technically ought to be
> "64-bit" anyways, since it's constrained to be the same as the 64-bit
> "input register".  That means that you ought to make sure to set
> *both* output registers appropriately, one of them being 0 and the
> other being the 32-bit number.  I think that's the only answer that
> actually makes any sense from a holistic code-generation sense.  So it
> seems we are in violent agreement :-D.
> 

No.

This is wrong on two accounts.

First of all, THERE ARE NO "TWO OUTPUT REGISTERS".  Period.  There is 
only one.  The question is: which of the two *input* registers does it 
correspond to?

Second of all, "making sense from a holistic code-generation sense" 
doesn't apply here.  This is about mimicing a gcc construct, regardless 
of which amount of sense it makes.  Therefore, the only thing that 
actually makes sense is to mimic gcc behavior, no matter how stupid it 
happens to be.

	-hpa

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ