* Fix #APP handling for iq2000-elf port
@ 2005-03-03 13:02 Nick Clifton
0 siblings, 0 replies; only message in thread
From: Nick Clifton @ 2005-03-03 13:02 UTC (permalink / raw)
To: binutils
Hi Guys,
I am applying the patch below to fix up the iq2000-elf port's
handling of the #APP and #NO_APP directives. The problem was that
the iq2000 port has the hash character as a comment character but
not a line comment character and the #APP processing code relies
upon it being included in the line comment characters.
Possibly the #APP processing code ought to be reworked to allow for
the situation where # is just a comment character, but all other
ports that use it have it in both comment_chars and
line_comment_chars and this close to a branch I do not want to rock
the boat.
Cheers
Nick
gas/ChangeLog
2005-03-03 Nick Clifton <nickc@redhat.com>
* config/tc-iq2000.c (line_comment_chars): Include the # character
as otherwise this breaks #APP/#NO_APP processing.
Index: gas/config/tc-iq2000.c
===================================================================
RCS file: /cvs/src/src/gas/config/tc-iq2000.c,v
retrieving revision 1.6
diff -c -3 -p -r1.6 tc-iq2000.c
*** gas/config/tc-iq2000.c 12 Jan 2005 10:57:15 -0000 1.6
--- gas/config/tc-iq2000.c 3 Mar 2005 13:01:51 -0000
*************** typedef struct
*** 55,61 ****
iq2000_insn;
const char comment_chars[] = "#";
! const char line_comment_chars[] = "";
const char line_separator_chars[] = ";";
const char EXP_CHARS[] = "eE";
const char FLT_CHARS[] = "dD";
--- 55,61 ----
iq2000_insn;
const char comment_chars[] = "#";
! const char line_comment_chars[] = "#";
const char line_separator_chars[] = ";";
const char EXP_CHARS[] = "eE";
const char FLT_CHARS[] = "dD";
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-03-03 13:02 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-03-03 13:02 Fix #APP handling for iq2000-elf port Nick Clifton
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).