public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Azael Developer <azael.devel@gmail.com>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sourceware.org, A Receiver <azael.rmartz@gmail.com>
Subject: Re: Gas developing
Date: Mon, 22 Jan 2024 08:57:32 -0800	[thread overview]
Message-ID: <CABF4CRjs7aPfbpX3aLc047-wX=VA4S+BSAwErdAzDmHe56ag3g@mail.gmail.com> (raw)
In-Reply-To: <9d5db367-00c8-4c44-ac2e-2bf76dda8c04@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1491 bytes --]

Thanks for the advice Nick

On Mon, Jan 22, 2024 at 8:51 AM Nick Clifton <nickc@redhat.com> wrote:

> Hi Azael,
>
> > 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.
>
> Also please be prepared for the fact that creating a fully functional
> assembler is no small task.  You will find that it will take up a
> lot of your time.
>
> As a suggestion I would restrict yourself to just supporting the
> ELF file format and the DWARF debug format.  There are other
> formats out there, but only supporting one does make things simpler.
> Plus you may be able to take advantage of packages like the elfutils
> which provide libraries for manipulating ELF and DWARF.
>
> Another suggestion is to steal, sorry I mean borrow, all of the
> tests used by the other assemblers.  Make sure that your assembler
> can pass those tests too.  That should give you great confidence
> that the assembler works.
>
> Oh and one more thing - document everything.  Good documentation
> and good comments are the key to a long lived open source project.
>
> Cheers
>    Nick
>
>

  reply	other threads:[~2024-01-22 16:57 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 [this message]
2024-01-22 17:25   ` Mike Frysinger
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='CABF4CRjs7aPfbpX3aLc047-wX=VA4S+BSAwErdAzDmHe56ag3g@mail.gmail.com' \
    --to=azael.devel@gmail.com \
    --cc=azael.rmartz@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.com \
    /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).