From: Mike Frysinger <vapier@gentoo.org>
To: Azael Developer <azael.devel@gmail.com>
Cc: binutils@sourceware.org, A Receiver <azael.rmartz@gmail.com>
Subject: Re: Gas developing
Date: Mon, 22 Jan 2024 12:25:05 -0500 [thread overview]
Message-ID: <Za6k8Z3iGJu_p2je@vapier> (raw)
In-Reply-To: <9d5db367-00c8-4c44-ac2e-2bf76dda8c04@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]
On 22 Jan 2024 16:51, Nick Clifton wrote:
> > now I want to create a useful assembler with new capabilities, even I want to add a high level assembler like a C/C++ syntaxes, all that to support the open source movement.
>
> Well I wish you luck. I feel that I should point out that there
> are already two open source assemblers available - the one from
> the GNU binutils project and the one from the LLVM project. So
> you probably need to have some feature to make yours stand out.
there's even more if the target is x86 -- nasm/yasm, and masm (Windows).
there's also dev86 which hasn't been updated in a while, but seems to be
used in a few places still.
creating an assembler can certainly be a useful learning exercise. going
beyond that, everything Nick said is certainly true -- it's already a pretty
competitive landscape, so you'd want to identify a significant shortcoming
to make yours stand out as something people would care about.
just don't morph into something like High Level Assembly (HLA) :).
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-01-22 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 4:33 Azael Developer
2024-01-22 16:51 ` Nick Clifton
2024-01-22 16:57 ` Azael Developer
2024-01-22 17:25 ` Mike Frysinger [this message]
2024-01-22 18:37 ` Azael Developer
2024-01-22 20:30 ` Mike Frysinger
2024-01-22 18:44 ` Azael Developer
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=Za6k8Z3iGJu_p2je@vapier \
--to=vapier@gentoo.org \
--cc=azael.devel@gmail.com \
--cc=azael.rmartz@gmail.com \
--cc=binutils@sourceware.org \
/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).