I want to enable V extension on gcc-cross

[zhangze0722]

Description

Steps to reproduce the issue:
1.change SRC_URI in openembedded-core/meta/recipes-devtools/gcc/gcc-12.2.inc

SOURCEDIR ?= "git"
SRC_URI = "git://github.com/riscv-collab/riscv-gcc.git;protocol=https;branch=riscv-gcc-rvv-next"
SRCREV = "da01ba455ce3802ffa84fdca3a089079996dbfc3"

only this branch has V extension support, so source code change to this branch

add this line in gcc-configure-common.inc to enable V extension:

EXTRA_OECONF:append:riscv64 = " --with-arch-64=rv64gcv"

Describe the results you received:
but some package can not be built. could anyone give some advice? thanks.

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):

Additional details (revisions used, host distro, etc.):

Build Configuration:
BB_VERSION = "2.0.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "riscv64-unknown-linux"
MACHINE = "qemuriscv64"
DISTRO = "nodistro"
DISTRO_VERSION = "nodistro.0"
TUNE_FEATURES = "riscv64"
meta = "HEAD:42e414ad2204949bb70c3aa64503a6ef5681532d"
meta-oe
meta-python
meta-multimedia
meta-networking = "HEAD:fd4ae00b2bed08aca4ca21e83f12ea32bd527726"
meta-riscv = "HEAD:c5f397f37eadb1209ec39202b48a7592733aabd4"

[kraj]

@zhangze0722 this is a good candidate for your local customization, We perhaps want to wait for upstreaming these patches to gcc, or perhaps create separate gcc recipes which someone can select using GCCVERSION or some such.