public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: "Andreas K. Huettel" <dilfridge@gentoo.org>
Cc: libc-alpha <libc-alpha@sourceware.org>, toolchain@gentoo.org
Subject: Re: [2.33] FAIL: string/tst-memset-rtm
Date: Mon, 31 Jan 2022 15:36:19 -0800	[thread overview]
Message-ID: <CAMe9rOo2gt1tVWt7=bns1AQY5dffX886Bb71nH0mq8d0y4crig@mail.gmail.com> (raw)
In-Reply-To: <4463051.R56niFO833@pinacolada>

On Mon, Jan 31, 2022 at 2:57 PM Andreas K. Huettel via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> Hi all,
>
> so I just pulled recent 2.33 commits into our Gentoo 2.33 branch [*] and noticed a new
> test and a new fail...
>
> FAIL: string/tst-memset-rtm
>
> tst-memset-rtm.out says
> error: ../sysdeps/x86/tst-string-rtm.h:63: TSX abort rate: 100.00% (3000 out of 3000)
> error: 1 test failures
>
> Something to worry about?
>
> Linux pinacolada 5.15.16-gentoo #1 SMP PREEMPT Tue Jan 25 23:46:25 CET 2022 x86_64 Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz GenuineIntel GNU/Linux
> gcc (Gentoo 11.2.0 p1) 11.2.0
> GNU ld (Gentoo 2.37_p1 p0) 2.37

What processor are you using? Please show your /proc/cpuinfo

> Cheers,
> Andreas
>
> [*] See https://gitweb.gentoo.org/fork/glibc.git/log/?h=gentoo/2.33 for the exact
> changes; to be precise, from gentoo/glibc-2.33-8 to gentoo/glibc-2.33-9 tag.
>
> --
> Andreas K. Hüttel
> dilfridge@gentoo.org
> Gentoo Linux developer
> (council, toolchain, base-system, perl, libreoffice)



-- 
H.J.

  reply	other threads:[~2022-01-31 23:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 22:56 Andreas K. Huettel
2022-01-31 23:36 ` H.J. Lu [this message]
2022-02-01  7:29   ` Andreas K. Huettel
2022-02-01  8:04     ` Noah Goldstein
2022-02-01 14:09       ` H.J. Lu
2022-02-01 20:40         ` Andreas K. Huettel

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='CAMe9rOo2gt1tVWt7=bns1AQY5dffX886Bb71nH0mq8d0y4crig@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=dilfridge@gentoo.org \
    --cc=libc-alpha@sourceware.org \
    --cc=toolchain@gentoo.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).