From: Azael Developer <azael.devel@gmail.com>
To: binutils@sourceware.org
Cc: A Receiver <azael.rmartz@gmail.com>
Subject: Gas developing
Date: Thu, 18 Jan 2024 20:33:43 -0800 [thread overview]
Message-ID: <CABF4CRgVVQHXAGV8dPp9wwgqegQJFuWHhFdJgQcsVtztYpUDqw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 468 bytes --]
Few weeks ago I write a little assembler like a experiment, it's very basic
, but it has been help me to understand the problem to accomplish that, now
I want to create a useful assembler with new capabilities, even I want to
add a high level assembler like a C/C++ sintaxis, all that to support the
open source movement. I think in include a large list of processor. So I
going to be grateful if someone tell me what think the binutils project
about this possibility
next reply other threads:[~2024-01-19 4:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 4:33 Azael Developer [this message]
2024-01-22 16:51 ` Nick Clifton
2024-01-22 16:57 ` Azael Developer
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=CABF4CRgVVQHXAGV8dPp9wwgqegQJFuWHhFdJgQcsVtztYpUDqw@mail.gmail.com \
--to=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).