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=-3.3 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 8177 invoked from network); 18 Jun 2020 21:43:05 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 18 Jun 2020 21:43:05 -0000 Received: (qmail 25949 invoked by uid 550); 18 Jun 2020 21:42:59 -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 25931 invoked from network); 18 Jun 2020 21:42:59 -0000 Date: Thu, 18 Jun 2020 23:42:47 +0200 From: Szabolcs Nagy To: sidneym@codeaurora.org Cc: musl@lists.openwall.com Message-ID: <20200618214247.GD2048759@port70.net> Mail-Followup-To: sidneym@codeaurora.org, musl@lists.openwall.com References: <029101d6134e$56d4ece0$047ec6a0$@codeaurora.org> <20200415180620.GA23945@port70.net> <20200415182619.GI11469@brightrain.aerifal.cx> <039701d61359$c56efa50$504ceef0$@codeaurora.org> <20200415192940.GJ11469@brightrain.aerifal.cx> <005a01d61f40$dc8cc7b0$95a65710$@codeaurora.org> <20200430235109.GJ21576@brightrain.aerifal.cx> <8c3611dcf8e2c59885fecd9ebdc70d79@codeaurora.org> <20200506005929.GG21576@brightrain.aerifal.cx> <1a0301d6458e$b4264d90$1c72e8b0$@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1a0301d6458e$b4264d90$1c72e8b0$@codeaurora.org> Subject: Re: [musl] Hexagon DSP support * sidneym@codeaurora.org [2020-06-18 11:37:05 -0500]: > I attached the updated REPORT with warning output disabled, -w and > -fno-rounding-math (See https://bugs.llvm.org/show_bug.cgi?id=45329) along > with the patch. I've rebased a couple of times without any conflicts and > the git repo is here: https://github.com/quic/musl/tree/hexagon the fmal failures are a bit concerning: fmal should be a tail call to fma if long double has the same representation as double. (can you please verify this? there should be a single branch instruction in fmal) there are no fma failures with the same tests so fmal should work fine too. may be the libc-test code got miscompiled or somehow wrong? or long double arithmetics is broken?