From: Ian Lance Taylor <iant@google.com>
To: Ivan Pryanishnikov <prianich@complang.tuwien.ac.at>
Cc: binutils@sourceware.org
Subject: Re: GAS parser
Date: Thu, 02 Aug 2007 17:52:00 -0000 [thread overview]
Message-ID: <m3fy31ddvj.fsf@localhost.localdomain> (raw)
In-Reply-To: <20070802135244.GA23349@complang.tuwien.ac.at>
Ivan Pryanishnikov <prianich@complang.tuwien.ac.at> writes:
> I have a question concerning GAS: some ports (eg, bfin) use
> lex/bison extensions (eg, bfin-lex.l, bfin-parse.y) to write their
> parsers.
>
> I was wandering about the reasons behind; possibly some of them
> are:
> - it's easier (generally) in some sense
> - it's not possible to solve their parsing problems in a standard way
> - they had some non-gnu assembler and just adjust/reuse it for the
> binutils assembler (because it's easier than to write from scratch)
> - ??
I don't know about bfin. For m68k Ken and I wrote a Bison parser
(though not a flex lexer) because the assembler needed to support two
different syntaxes, and the cases were sufficiently complex that it
seemed worthwhile to express them in a grammar, to minimize the chance
of error. So I guess that your option 1 applies for the m68k.
Ian
next prev parent reply other threads:[~2007-08-02 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 13:52 Ivan Pryanishnikov
2007-08-02 17:52 ` Ian Lance Taylor [this message]
2007-08-04 9:44 ` l l
2007-08-06 1:12 ` Dave Korn
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=m3fy31ddvj.fsf@localhost.localdomain \
--to=iant@google.com \
--cc=binutils@sourceware.org \
--cc=prianich@complang.tuwien.ac.at \
/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).