All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johann Oskarsson <myrkraverk@users.sourceforge.net>
To: hp <lx@lxhp.in-berlin.de>, linux-assembly@vger.kernel.org
Subject: Re: Preprocessing Assembly
Date: Fri, 02 May 2003 19:22:53 +0000	[thread overview]
Message-ID: <3EB2C58D.60005@users.sourceforge.net> (raw)
In-Reply-To: 200304300633.h3U6XA9L031703@hirsch.in-berlin.de

Hi,

MASP can now be found on the web: 
http://cosmos.raunvis.hi.is/~johannos/masp/
This is just a trial version so far.  The only changes are that 
directives now start with \ instead of ., so this no longer conflicts 
with the underlying assembler.  And mips directives in particular.  I've 
yet to add a command line parameter to change this char, but it can be 
done easily.

hp wrote:

>[snip]
>
>some versions of CPP insert a blank after "<<".
>thus you can't use a '#define'd string which contains multiple text elements 
>as a macro argument w. GASP because of it's  (imho) very silly delimiting 
>convention which takes a comma as well as a blank space for the .macro 
>arguments delimiter but provides no means to pass a parameter which consists 
>of more than a single piece of text. NO way round! no bracees, brackets... 
>  
>
I'll try to fix this one day, don't know if it'll be soon though.

>[snip]
>
>further, the temporary radix setting of GASP is un-useable. 
>	movl $H'12345,eax	(I tried any possible variant)
>
I've changed the base syntax in masp, it now uses 0[bhqd]<number> for 
strange bases instead of the ugly [BHQD]'<number> syntax.  Although I 
haven't released that version yet, I can do so now and/or emailed it if 
anyone asks.  This also means that 'c' character constants can now be 
passed to the assembler.

>[snip]
>
>imho, due to bad design:
>macro args can't be addressed by their numeric position in the arguments list.
>no means to analyzing the addressing mode of an argument.
>no cross-ref listing (something similar, which most often is quite useless).
>
I'm not sure if/when I can address this, most of the changes I make, is 
to fix something that simply pisses me off!

>[snip]
>
>...(more in the list included in the F4 archive)...
>
>just mentioned. I'll leave that for later...
>
I haven't had a close look on the F4 but I will perhaps in the future.


Johann


P.S. You've mentioned a lot of stuff, and I wish I could fix them all 
but I'm still familiarizing myself with the code and capabilities of 
gasp.  I can perhaps do more if you try masp and send me some bug reports.


      reply	other threads:[~2003-05-02 19:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-26 15:16 Preprocessing Assembly Johann Oskarsson
2003-04-27  0:20 ` hp
2003-04-27  2:51   ` Johann Oskarsson
2003-04-27 11:29     ` hp
2003-04-30  0:08       ` Johann Oskarsson
2003-04-30  7:32         ` hp
2003-05-02 19:22           ` Johann Oskarsson [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=3EB2C58D.60005@users.sourceforge.net \
    --to=myrkraverk@users.sourceforge.net \
    --cc=linux-assembly@vger.kernel.org \
    --cc=lx@lxhp.in-berlin.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.