public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
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 15:30:54 -0500	[thread overview]
Message-ID: <Za7QfhYOY0o1Cp8J@vapier> (raw)
In-Reply-To: <CABF4CRjt0R4iLBWv9ns_U8DnU_EAM0sdgi2rhq7W4eWQYHgYgg@mail.gmail.com>

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

On 22 Jan 2024 10:37, Azael Developer wrote:
> I was thinking of an update for GAS, not a competition with other
> compilers. I was really hoping that the project had some plans about
> it,

tbh, i think gas is a "finished" assembler at this point, and most new
work is going into other places like language frontends.  i don't think
the project is anti new-features, it's more "who is the audience" for
such changes, and does it make more sense to put things into gas vs just
(ab)using the preprocessor to largely get the same benefit.  e.g. it's
pretty common to create a .S file to run through cpp and gain benefit
from the various define's that the arch backend provides to produce the
.s file that gets fed to the assembler.  there are cases where i don't
have a preprocessor and can only write .s, but it's pretty uncommon.

personally i wish the macro language was a bit easier to use.

or you could see our existing gas bug list and whether there's any
feature requests that are interesting.
https://sourceware.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&component=gas&list_id=80426&order=Importance&product=binutils&query_format=advanced
-mike

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-01-22 20:30 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
2024-01-22 18:37     ` Azael Developer
2024-01-22 20:30       ` Mike Frysinger [this message]
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=Za7QfhYOY0o1Cp8J@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).