| 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
| ||
|
Message-Id: <200707231837.27592.ak@suse.de> Date: Mon, 23 Jul 2007 18:37:27 +0200 From: Andi Kleen <ak@...e.de> To: Satyam Sharma <ssatyam@....iitk.ac.in> Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, David Howells <dhowells@...hat.com>, Nick Piggin <nickpiggin@...oo.com.au>, Andrew Morton <akpm@...ux-foundation.org>, Linus Torvalds <torvalds@...ux-foundation.org>, jh@...e.cz Subject: Re: [PATCH 3/8] i386: bitops: Rectify bogus "+m" constraints On Monday 23 July 2007 18:05:43 Satyam Sharma wrote: > From: Satyam Sharma <ssatyam@....iitk.ac.in> > > [3/8] i386: bitops: Rectify bogus "+m" constraints > > From the gcc manual: > > Extended asm supports input-output or read-write operands. Use the > constraint character `+' to indicate such an operand and list it with > the output operands. You should only use read-write operands when the > constraints for the operand (or the operand in which only some of the > bits are to be changed) allow a register. > > So, using the "+" constraint modifier for memory, like "+m" is bogus. > We must simply specify "=m" which handles the case correctly. I checked with Honza (cc'ed) and he stated that the + are really needed at least in newer gcc. -Andi - 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