public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@zembu.com>
To: utz@serv.net
Cc: dh@ctechnologies.se, ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Macro problems in arm-elf-as
Date: Tue, 15 Jun 1999 15:18:00 -0000	[thread overview]
Message-ID: <19990615221634.14985.qmail@daffy.airs.com> (raw)
In-Reply-To: <Pine.BSF.4.02.9906151430310.3393-100000@itchy.serv.net>

   Date: Tue, 15 Jun 1999 14:40:45 -0700 (PDT)
   From: The Utz Family <utz@serv.net>

   could somebody work arounds this by preprocessing? comments get stripped
   prior to compilation, so if somebody were to preprocess this independent
   of as and the feed it to as after processing ( assuming that there is a
   flag that tells as that it will be receiving predigested input ).....

Yes, there is such a flag: -f.  However, that flag normally requires
that the assembler input follow a fairly precise format (.e.g, no
multiple consecutive spaces), and is generally only intended to be
used when assembling compiler output.

   my other tremendously lame suggestion is to go in and hack the code to 
   turn off comment processing in the parser and not use any comments ( thats
   pure heresy to me, but it doesnt mean that you couln't have the comments
   in the checked in copy for now, and then just strip them with a perl
   script or something...... ) 

You'll still have line comments: if the first character on the line is
`#', the ARM assembler will ignore the line.  The `@' character is
different because it works anywhere that it appears.  You can easily
disable the special handling of `@' by changing comment_chars in
gas/config/tc-arm.c.  But your code won't work with an unhacked
assembler.

Ian

      reply	other threads:[~1999-06-15 15:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-15  4:26 Dan Hovang
1999-06-15  9:45 ` Ian Lance Taylor
1999-06-15 14:40   ` The Utz Family
1999-06-15 15:18     ` Ian Lance Taylor [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19990615221634.14985.qmail@daffy.airs.com \
    --to=ian@zembu.com \
    --cc=dh@ctechnologies.se \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=utz@serv.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).