From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-sender-0.a4lg.com (mail-sender-0.a4lg.com [IPv6:2401:2500:203:30b:4000:6bfe:4757:0]) by sourceware.org (Postfix) with ESMTPS id F05173858D3C for ; Tue, 29 Aug 2023 08:54:41 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org F05173858D3C Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=irq.a4lg.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=irq.a4lg.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by mail-sender-0.a4lg.com (Postfix) with ESMTPSA id C9E13300089; Tue, 29 Aug 2023 08:54:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=irq.a4lg.com; s=2017s01; t=1693299278; bh=ggKQv0+1oAW0Huo6qHYhj2IJlRL1zR+rknenwe2w9kE=; h=Message-ID:Date:Mime-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=D2ZgJIrc1HwmWy/k9jYwY0VnfFSfI239jPn9kxINCV92H/Wj85sFvuDv9fdSYFMQl IHfbvaa0h0H/pxbA4w18PNayT+GOUIPwqkW2gANCeYQQOeD/eI/2UmpAQEjmxXa+si r0jSFKiJ4Q0F7SpOwXK52nc5fdMLfwSrO912db7U= Message-ID: Date: Tue, 29 Aug 2023 17:54:38 +0900 Mime-Version: 1.0 Subject: Re: [PATCH 1/1] RISC-V: Imply 'Zicsr' from 'Zcmt' Content-Language: en-US To: Kito Cheng Cc: gcc-patches@gcc.gnu.org References: <1c4f3e947919e720c18e5af9ecc7b6b76e06611a.1693280446.git.research_trasio@irq.a4lg.com> From: Tsukasa OI In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-12.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,GIT_PATCH_0,KAM_SHORT,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 2023/08/29 17:42, Kito Cheng wrote: > LGTM, did you have commit access for GCC repo? you should obtain it if > you don't have it yet, I think you are already an important member of > the RISC-V GNU toolchain community :) Not yet (only Binutils/GDB). Jeff is mainly merging my changes to the trunk so far. Thanks for mentioning and sponsoring me for write access to GCC. I truly appreciate that mentioning me as an important member and write access to the GCC repository will be also helpful. I'll contact GCC overseers later. Sincerely, Tsukasa > > https://gcc.gnu.org/gitwrite.html#authenticated , and you can add me > to the cc list as your sponsor. > > > > On Tue, Aug 29, 2023 at 11:42 AM Tsukasa OI via Gcc-patches > wrote: >> >> From: Tsukasa OI >> >> As the specification states, the 'Zcmt' extension depends on the 'Zca' and >> 'Zicsr' extensions. This commit reflects this implication. >> >> gcc/ChangeLog: >> >> * common/config/riscv/riscv-common.cc >> (riscv_implied_info): Add implication from 'Zcmt' to 'Zicsr'. >> --- >> gcc/common/config/riscv/riscv-common.cc | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/gcc/common/config/riscv/riscv-common.cc b/gcc/common/config/riscv/riscv-common.cc >> index a5b62cda3a09..1315c8a745ec 100644 >> --- a/gcc/common/config/riscv/riscv-common.cc >> +++ b/gcc/common/config/riscv/riscv-common.cc >> @@ -142,6 +142,7 @@ static const riscv_implied_info_t riscv_implied_info[] = >> {"zcb", "zca"}, >> {"zcmp", "zca"}, >> {"zcmt", "zca"}, >> + {"zcmt", "zicsr"}, >> >> {NULL, NULL} >> }; >> -- >> 2.42.0 >> >