This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: demand_empty_rest_of_line and ignore_rest_of_line


On Mon, 26 Apr 2004, Ian Lance Taylor wrote:
> Richard Earnshaw <Richard.Earnshaw@arm.com> writes:
>
    Andreas Schwab wrote:
> > > Currently (gcc 3.4.0) there are 5 targets that actually make use of
> > > #NO_APP: arm, cris, m68k, ns32k and vax (and m68k-linux didn't in gcc
> > > 3.0.x upto 3.3.x due to a side effect of including "elfos.h", which
> > > redefines ASM_FILE_START).
> >
> > That's probably misleading.  The gcc might emit a directive for that,
> > but I'm almost certain the ARM assembler for one takes no notice of it.
>
> The code to handle #NO_APP in gas is independent of the CPU backend.
> The initial #NO_APP comment is recognized in input_file_open(); it
> must be the first characters in the file.  It then turns off
> preprocessing (i.e., calls to do_scrub_chars) except for code which
> follows #APP up to #NO_APP.
>
> That said, I don't see #NO_APP in assembler code generated by an
> xscale-elf compiler.

(I already mentioned, but some apparently missed it or
--hopefully not-- disbelieved it, so let me repeat anyway, that)
I checked arm-linux main trunk, confirming that *no* #NO_APP is
generated at the top of the generated assembly files.

I'm reluctant to accept the list above (except for CRIS and
m68k from previous checking) without checking myself. ;-)

brgds, H-P


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]