From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 2162 invoked from network); 10 Nov 2022 17:19:21 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 10 Nov 2022 17:19:21 -0000 Received: (qmail 30104 invoked by uid 550); 10 Nov 2022 17:19:18 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 30069 invoked from network); 10 Nov 2022 17:19:17 -0000 Date: Thu, 10 Nov 2022 12:18:58 -0500 From: Rich Felker To: enh Cc: musl@lists.openwall.com Message-ID: <20221110171858.GJ29905@brightrain.aerifal.cx> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] SA_RESTORER for rv64? On Thu, Nov 10, 2022 at 07:44:23AM -0800, enh wrote: > arch/riscv64/bits/signal.h has contained a definition for SA_RESTORER since > the initial commit, but i think that's just copy & paste from whichever > architecture the rv64 headers were based on? the linux kernel itself > doesn't have SA_RESTORER for rv64, unless i'm missing something? I suspect this is just a mistake. Have you seen any ill effects from it? If riscv folks can confirm it's wrong, I'll remove it. Rich