public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
	 libc-alpha@sourceware.org
Cc: caiyinyu <caiyinyu@loongson.cn>, Wang Xuerui <i@xen0n.name>
Subject: Re: [PATCH] LoongArch: Add math-barriers.h
Date: Mon, 27 Feb 2023 18:45:29 +0800	[thread overview]
Message-ID: <49d31729ad3375dcd1632fc5e4f0621e458afd90.camel@xry111.site> (raw)
In-Reply-To: <712299a4-2fd2-936d-a016-3557ea8f48d6@linaro.org>

On Thu, 2023-02-16 at 10:43 -0300, Adhemerval Zanella Netto wrote:
> 
> 
> On 16/02/23 10:02, Xi Ruoyao wrote:
> > On Wed, 2023-02-15 at 11:25 -0300, Adhemerval Zanella Netto wrote:
> > > 
> > > I meant that I saw math/test-fenv failures with and without the
> > > patch
> > > and I the master qemu (f670b3eec7f5d1ed8c4573ef244e7b8c6b32001b).
> > 
> > Hi Adhemerval,
> > 
> > Which GCC version did you used?  I'll try with the same GCC version
> > on
> > the hardware. If it still fails I'll consider it a QEMU issue and
> > report
> > to QEMU maintainers.
> > 
> 
> This is the one I used:
> 
> gcc version 12.1.1 20220719 [releases/gcc-12 r12-8552-g65941a91091]
> (GCC)

On a hardware (3A5000-7A2000-EVB) the test passes with the same GCC.  My
first guess would be a QEMU issue.  There could be a difference in
Binutils version but I don't think a Binutils difference can cause fenv
failure...

BTW could you (or Yinyu) push the patch?  I don't have a write access of
glibc.git (yet).

-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

  reply	other threads:[~2023-02-27 10:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14  8:57 Xi Ruoyao
2023-02-15 13:47 ` Adhemerval Zanella Netto
2023-02-15 14:22   ` Xi Ruoyao
2023-02-15 14:25     ` Adhemerval Zanella Netto
2023-02-16 13:02       ` Xi Ruoyao
2023-02-16 13:43         ` Adhemerval Zanella Netto
2023-02-27 10:45           ` Xi Ruoyao [this message]
2023-02-27 11:23             ` Adhemerval Zanella Netto
2023-02-27 11:25               ` WANG Xuerui

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49d31729ad3375dcd1632fc5e4f0621e458afd90.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=adhemerval.zanella@linaro.org \
    --cc=caiyinyu@loongson.cn \
    --cc=i@xen0n.name \
    --cc=libc-alpha@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).