riscv64: -march=rv64gcv1p0 vs <riscv_vector.h>

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: gcc-help <gcc-help@xxxxxxxxxxx>
Subject: riscv64: -march=rv64gcv1p0 vs <riscv_vector.h>
From: Mathieu Malaterre via Gcc-help <gcc-help@xxxxxxxxxxx>
Date: Tue, 2 Aug 2022 19:01:39 +0200
In-reply-to: <CA+7wUsxmWnx0RJk=sNsANV7gXY+uZCDV=t9hCcJ7k=Em=qcjSQ@mail.gmail.com>
References: <CA+7wUsxmWnx0RJk=sNsANV7gXY+uZCDV=t9hCcJ7k=Em=qcjSQ@mail.gmail.com>
Reply-to: Mathieu Malaterre <mathieu.malaterre@xxxxxxxxx>

Hi all,

I see that GCC-12 now accepts `-march=rv64gcv1p0` but at the same time
does not provide a header file for `riscv_vector.h`.

Could someone please confirm this is a known issue ?

Thanks

-- 
Mathieu

References:
- riscv64: -march=rv64gcv1p0 vs <riscv_vector.h>
  - From: Mathieu Malaterre

Prev by Date: Re: determining impact of vulnerability CVE-2022-27943 in libiberty/rust-demangle.c
Next by Date: riscv64: -march=rv64gcv1p0 vs riscv_vector.h
Previous by thread: riscv64: -march=rv64gcv1p0 vs <riscv_vector.h>
Next by thread: determining impact of vulnerability CVE-2022-27943 in libiberty/rust-demangle.c
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]

Powered by Linux