* bit_fix.h: Likewise.
* expr.c: Likewise.
* itbl-ops.c: Likewise.
+2001-10-11 Kazu Hirata <kazu@hxi.com>
+
+ * app.c: Fix comment typos.
+ * bit_fix.h: Likewise.
+ * expr.c: Likewise.
+ * itbl-ops.c: Likewise.
+
2001-10-11 Nick Clifton <nickc@cambridge.redhat.com>
* input-file.c: Include safe-ctype.h.
/* I added states 9 and 10 because the MIPS ECOFF assembler uses
constructs like ``.loc 1 20''. This was turning into ``.loc
120''. States 9 and 10 ensure that a space is never dropped in
- between characters which could appear in a identifier. Ian
+ between characters which could appear in an identifier. Ian
Taylor, ian@cygnus.com.
I added state 11 so that something like "Lfoo add %r25,%r26,%r27" works
/* bit_fix.h
- Copyright 1987, 1992, 2000 Free Software Foundation, Inc.
+ Copyright 1987, 1992, 2000, 2001 Free Software Foundation, Inc.
This file is part of GAS, the GNU Assembler.
ns32k port.
The acbi, addqi, movqi, cmpqi instruction requires an assembler that
can handle bitfields. Ie handle an expression, evaluate it and insert
- the result in an some bitfield. ( ex: 5 bits in a short field of a opcode)
+ the result in an some bitfield. ( ex: 5 bits in a short field of an opcode)
*/
#ifndef __bit_fix_h__
/* In: Input_line_pointer points to 1st char of operand, which may
be a space.
- Out: A expressionS.
+ Out: An expressionS.
The operand may have been empty: in this case X_op == O_absent.
Input_line_pointer->(next non-blank) char after operand. */
\f
/* Internal. Simplify a struct expression for use by expr (). */
-/* In: address of a expressionS.
+/* In: address of an expressionS.
The X_op field of the expressionS may only take certain values.
Elsewise we waste time special-case testing. Sigh. Ditto SEG_ABSENT.
Unary operators and parenthetical expressions are treated as operands.
As usual, Q==quantity==operand, O==operator, X==expression mnemonics.
- We used to do a aho/ullman shift-reduce parser, but the logic got so
+ We used to do an aho/ullman shift-reduce parser, but the logic got so
warped that I flushed it and wrote a recursive-descent parser instead.
Now things are stable, would anybody like to write a fast parser?
Most expressions are either register (which does not even reach here)
int processor;
if (!name || !*name)
- return 0; /* error! must have a opcode name/expr */
+ return 0; /* error! must have an opcode name/expr */
/* find entry in list of instructions for all processors */
for (processor = 0; processor < e_nprocs; processor++)