On Sun, 27 May 2001, Kevin D. Kissell wrote: > Fair enough. It was an offhand remark. But seriously, what does > the "R" constraint mean here? The only documentation I've got > (http://linux.fh-heilbronn.de/doku/GNU/docs/gcc/gcc_163.html#SEC163) `info gcc' has most relevant data, at least for 2.95.3. > says that "Q" through "U" are reserved for use with EXTRA_CONSTRAINT > in machine-dependent definitions of arbitrary operand types. When > and where does it get bound for MIPS gcc, and what is it supposed > to mean? If I compile this kind of fragment using a "m" constraint, > it seems to do the right thing, at least on my archaic native compiler. Is it gcc generating right code or gas expanding a macro? Try `gcc -S' -- for me "m" generates "lw $0,262144($2)", which is unacceptable when ".set noat" is in effect (and perfectly fine otherwise). -- + Maciej W. Rozycki, Technical University of Gdansk, Poland + +--------------------------------------------------------------+ + e-mail: macro@ds2.pg.gda.pl, PGP key available +
