From: Dmitry Selyutin <ghostmansd@gmail.com>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: Alan Modra <amodra@gmail.com>, binutils@sourceware.org
Subject: Re: PPC binutils opcodes
Date: Wed, 11 May 2022 23:06:38 +0300 [thread overview]
Message-ID: <CAMqzjesBbTdGO8LoANZdET9J_FJsd4oWi5npA+mKY6KWpOZ9Qw@mail.gmail.com> (raw)
In-Reply-To: <CAPweEDzEuCbq5PwHCF+gG2mSbTQQTtm2N66VC=eP6BcaFwSQ0A@mail.gmail.com>
On Wed, May 11, 2022 at 10:46 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
> is there a "--draft" or "--experimental" flag
> that can be set?
> or is it something that is fine under a new CPU name (e.g. -mlibresoc)?
It seems that these are logically the same from the point of binutils:
it even looks like there are -future, as well as stuff like -mspe and
-mvle. We, for now, use -mlibresoc[0]. So, as a matter of fact, there
is, and we use it. But I'd also be interested to know whether this
should be handled differently than it is now.
[0] https://git.libre-soc.org/?p=binutils-gdb.git;a=commit;h=a1e12c31e28e8c630ad129fd672c25779b360d5f
next prev parent reply other threads:[~2022-05-11 20:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 9:24 Dmitry Selyutin
2022-05-11 10:09 ` Luke Kenneth Casson Leighton
2022-05-11 13:13 ` Alan Modra
2022-05-11 16:39 ` Dmitry Selyutin
2022-05-11 19:46 ` Luke Kenneth Casson Leighton
2022-05-11 20:06 ` Dmitry Selyutin [this message]
2022-05-12 6:32 ` lkcl
2022-05-15 17:38 ` Luke Kenneth Casson Leighton
2022-05-11 23:38 ` Alan Modra
2022-05-18 3:20 ` Peter Bergner
2022-05-18 9:57 ` Luke Kenneth Casson Leighton
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=CAMqzjesBbTdGO8LoANZdET9J_FJsd4oWi5npA+mKY6KWpOZ9Qw@mail.gmail.com \
--to=ghostmansd@gmail.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=lkcl@lkcl.net \
/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).