public inbox for
 help / color / mirror / Atom feed
From: jacob navia <>
To: Jan Beulich <>
Subject: Re: P.S. Follow up to my last post
Date: Fri, 25 Aug 2023 15:07:18 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

OK, there is no bug, I didn’t expect anything else.


To use all the instruction of the processor he/she is running on, the user should:

1)Be aware that gcc doesn’t see crucial instructions of the processor by verifying its assembler output.

2) Be aware that there is an (undocumented) option -march… that will enable the assembler and the compiler to generate all the instructions of the current processor.

Well, there is NO BUG!

This is by design then.

Thank you very much.


> Le 25 août 2023 à 14:00, Jan Beulich <> a écrit :
> On 25.08.2023 13:52, jacob navia wrote:
>> The lack of the Ebb instructions is CRUCIAL for performance when accessing tables / arrays!
>> This instructions allow to combine an addition and a shift by 1, 2 or 3, to access tables of shorts, ints or doubles.
>> This speeds up the access to tables enormously and would allow gcc to generate much better code.
> Since you're writing to binutils@, you may want to also mention what gas
> bug you think you see. So far (also in the other mail) you've talked of
> only gcc. If you meant to say that like in gcc you need to enable use of
> the instructions in gas, then yes, that's the way the RISC-V assembler
> works (like e.g. also the PPC one, but unlike e.g. the x86 one).
> Jan

  reply	other threads:[~2023-08-25 13:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 11:52 jacob navia
2023-08-25 12:00 ` Jan Beulich
2023-08-25 13:07   ` jacob navia [this message]
2023-08-25 13:30     ` Jan Beulich
2023-08-25 13:40       ` Paul Koning
     [not found] <>
2023-08-25 15:32 ` Palmer Dabbelt
2023-08-25 16:10   ` jacob navia
2023-08-25 17:03     ` Paul Koning
2023-08-25 19:44       ` jacob navia
2023-08-28  6:17         ` Jan Beulich
2023-08-28  7:04           ` jacob navia

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).