1. Tech-Privileged
  2. Topics

回复：[RISC-V] [tech-privileged] [RFC] Toolchain interface for privilege spec related stuff.

"戎杰杰
 

Hi Krste,

    Sounds good.
    
    Also we are talking with @Philipp about how to keep compatible with vector v0.7.1 on toolchain interface,
    we suggest that we prefer this method to control it, e.g. -march=rv64gcv0p7 to specify vector v0.7.1,
   
    i think it's more consistent also,
    whether we use the 'v' extension with version number rather than 'x' extension to implement the requirement ?

--Jojo R

------------------------------------------------------------------
发件人：Krste Asanovic <krste@...>
发送时间：2021年8月28日(星期六) 04:45
收件人：Greg Favor <gfavor@...>
抄　送：Kito Cheng <kito.cheng@...>; Allen Baum <allen.baum@...>; mark <markhimelstein@...>; Philipp Tomsich <philipp.tomsich@...>; tech-privileged <tech-privileged@...>
主　题：Re: [RISC-V] [tech-privileged] [RFC] Toolchain interface for privilege spec related stuff.

Yes, that was the plan,
Krste

>>>>> On Fri, 27 Aug 2021 13:37:13 -0700, "Greg Favor" <gfavor@...> said:

| On Thu, Aug 26, 2021 at 8:31 PM Kito Cheng <kito.cheng@...> wrote:
|     For non-priverage extension, toolchain can control version for each
|     extension by ISA string, e.g. -march=rv64gcv0p10 to specify vector
|     extension with version 0.10.

| Should I assume that for the ratified vector spec simply 'v' can be specified?  And that a version number is only needed to refer to a pre-ratified version of the vector
| spec?

| Greg

|



1 - 1 of 1