This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: An ia32 LOCK/XADD bug.
- To: "H . J . Lu" <hjl at lucon dot org>
- Subject: Re: An ia32 LOCK/XADD bug.
- From: "Maciej W. Rozycki" <macro at ds2 dot pg dot gda dot pl>
- Date: Thu, 17 May 2001 11:32:32 +0200 (MET DST)
- cc: Ulrich Drepper <drepper at cygnus dot com>, GNU C Library <libc-alpha at sourceware dot cygnus dot com>, binutils at sourceware dot cygnus dot com
- Organization: Technical University of Gdansk
On Thu, 17 May 2001, H . J . Lu wrote:
> > > 2. If "lock xadd %edx,%edx" is really an illegal instruction on ia32,
> > > how should we fix gas to detect that?
> >
> > Some IA-32 specific code has to check that an instruction with a lock
> > prefix always has a memory operand. Don't know where to insert this.
>
> It may be tough. I can put in some testcases to make gas to fail :-).
I don't think such a check belongs to gas as "lock; xadd %edx,%edx" is
valid assembly code even if it faults when executed.
--
+ Maciej W. Rozycki, Technical University of Gdansk, Poland +
+--------------------------------------------------------------+
+ e-mail: macro@ds2.pg.gda.pl, PGP key available +