public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Daniel Schaefer" <daniel.schaefer@hpe.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"osteffen@redhat.com" <osteffen@redhat.com>
Cc: "Chang, Abner (HPS SW/FW Technologist)" <abner.chang@hpe.com>
Subject: Re: [edk2-devel] gcc 12, RiscV64 fence.i instruction missing
Date: Thu, 2 Jun 2022 14:34:16 +0000	[thread overview]
Message-ID: <SJ0PR84MB1505DA28F967FCA89A0DA763E0DE9@SJ0PR84MB1505.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20220602135034.xdauyepsbbjrpu3k@osteffen-laptop>

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

Hi Steffen,

No, I don't think we've tried GCC12 yet.
Hm, I don't quite understand the bug report but it sounds like something that'll be fixed by GCC?

Thanks,
Daniel
________________________________
From: devel@edk2.groups.io <devel@edk2.groups.io> on behalf of Oliver Steffen <osteffen@redhat.com>
Sent: Thursday, June 2, 2022 21:50
To: devel@edk2.groups.io <devel@edk2.groups.io>
Cc: Chang, Abner (HPS SW/FW Technologist) <abner.chang@hpe.com>
Subject: [edk2-devel] gcc 12, RiscV64 fence.i instruction missing

Hi,
has anyone tied building EDK2 (e.g. MdePkg) for RiscV64 with gcc 12?
I get:

/edk2/Build/Mde/DEBUG_GCC5/RISCV64/MdePkg/Library/BaseLib/BaseLib/OUTPUT/RiscV64/FlushCache.iiii:16: Error: unrecognized opcode `fence.i'

I found this gcc bug:
Bug 104853 - [RISC-V] -march=rv64g not including extension Zifencei
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104853

I was working on getting gcc 12 into the CI.

Thanks,
  Oliver







[-- Attachment #2: Type: text/html, Size: 2551 bytes --]

      reply	other threads:[~2022-06-02 14:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02 13:50 gcc 12, RiscV64 fence.i instruction missing Oliver Steffen
2022-06-02 14:34 ` Daniel Schaefer [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=SJ0PR84MB1505DA28F967FCA89A0DA763E0DE9@SJ0PR84MB1505.NAMPRD84.PROD.OUTLOOK.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