public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: Dhaval Sharma <dhaval@rivosinc.com>, devel@edk2.groups.io
Cc: Oliver Steffen <osteffen@redhat.com>
Subject: Re: [edk2-devel] [PATCH v5 2/2] OvmfPkg/RiscVVirt: Override for RV CPU Features
Date: Thu, 19 Oct 2023 17:51:04 +0200	[thread overview]
Message-ID: <60332378-d0f2-a915-ff60-782e5215aa4c@redhat.com> (raw)
In-Reply-To: <CAAxYnhRvBOSsLUY4_SPvN46Ph-JYvoe=VN0sJ=FUOWD0zHxztg@mail.gmail.com>

On 10/19/23 16:37, Dhaval Sharma wrote:
> It was introduced in 2.39 it seems.

Hm, then the macros should still be added please; RHEL9/EPEL9 only offer
binutils 2.38.

> GCC 12 onwards contains this
> binutils version as per my understanding.

No, gcc doesn't "contain" binutils. They are separate packages, and
their versions are not tightly locked together.

> This version was released
> quite long back. I can double check by submitting it through edk2 CI to
> ensure it works. Current CI version is already GCC 12.

It's the binutils version that matters for this.

(And even if CI has gcc-12, I'd still ask for the macros, because RHEL9
/ EPEL9 don't seem to have a new enough binutils.)

Thanks
Laszlo

> 
> On Thu, Oct 19, 2023 at 5:47 PM Laszlo Ersek <lersek@redhat.com
> <mailto:lersek@redhat.com>> wrote:
> 
>     On 10/19/23 11:22, Laszlo Ersek wrote:
>     > On 10/19/23 08:48, Dhaval Sharma wrote:
> 
>     >> (11) I agree that we should use symbolic names rather than
>     >> magic constants, but raw encodings of machine instructions don't
>     belong
>     >> into a
>     >>      C header file. [Dhaval] This bytecode was introduced
>     thinking what
>     >> if all compilers do not support it. but given the default compiler in
>     >> edk2 GCC 12 supports it
>     >>      we can eliminate this byte encoding completely to make it
>     easy and
>     >> simple to consume for others.
>     >
>     > To be honest, I can't determine the minimum expected gcc version for
>     > edk2. "BaseTools/Conf/tools_def.template" states a minimum version for
>     > NASM, for example, but I can't find a similar gcc requirement there.
>     >
>     > gcc-12 does work for me personally, because my riscv cross-compiler is
>     > "riscv64-linux-gnu-gcc (GCC) 12.1.1 20220507 (Red Hat Cross
>     12.1.1-1)".
>     >
>     > If the CI environment that builds these patches also provides gcc-12+,
>     > then I figure you should be set.
> 
>     Wait, for the assembly language source files, what matters is the
>     binutils version, not the gcc version. Mine is "GNU assembler version
>     2.38-3.el9" (from "binutils-riscv64-linux-gnu-2.38-3.el9.x86_64").
> 
>     Is that sufficient for the instuctions in question?
> 
>     (More generally -- what version does our CI env expect / provide?)
> 
>     Thanks
>     Laszlo
> 
> 
> 
> -- 
> Thanks!
> =D



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#109816): https://edk2.groups.io/g/devel/message/109816
Mute This Topic: https://groups.io/mt/102016149/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



      reply	other threads:[~2023-10-19 15:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17 12:17 [edk2-devel] [PATCH v5 0/2] MdePkg:Implement RISCV CMO Dhaval Sharma
2023-10-17 12:17 ` [edk2-devel] [PATCH v5 1/2] " Dhaval Sharma
2023-10-17 14:22   ` Laszlo Ersek
2023-10-17 14:32     ` Laszlo Ersek
2023-10-17 12:17 ` [edk2-devel] [PATCH v5 2/2] OvmfPkg/RiscVVirt: Override for RV CPU Features Dhaval Sharma
2023-10-17 14:25   ` Laszlo Ersek
2023-10-17 14:39   ` Laszlo Ersek
2023-10-19  6:48     ` Dhaval Sharma
2023-10-19  9:22       ` Laszlo Ersek
2023-10-19 12:17         ` Laszlo Ersek
2023-10-19 14:37           ` Dhaval Sharma
2023-10-19 15:51             ` Laszlo Ersek [this message]

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-list 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=60332378-d0f2-a915-ff60-782e5215aa4c@redhat.com \
    --to=devel@edk2.groups.io \
    /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