public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Paul Zimmermann <Paul.Zimmermann@inria.fr>
Cc: libc-alpha@sourceware.org
Subject: Re: make check failures on armv7l
Date: Tue, 18 May 2021 12:11:17 +0100	[thread overview]
Message-ID: <20210518111117.GR9028@arm.com> (raw)
In-Reply-To: <mweee4mhgy.fsf@tomate.loria.fr>

The 05/18/2021 13:03, Paul Zimmermann wrote:
> with glibc master f17164b I get some failures from make check, among which:
> 
> FAIL: elf/tst-glibc-hwcaps-prepend-cache

this is a regression since glibc 2.33
https://sourceware.org/bugzilla/show_bug.cgi?id=27046
(the only failure that keeps the armhf buildbot red)

> FAIL: stdio-common/tst-vfprintf-width-prec-mem

this works for me in my armhf tests.

> Glibc was configured with ../configure --prefix=/usr CC="gcc -march=native",
> configure says armv7l-unknown-linux-gnueabihf, and gcc is version 8.3.0.
> 
> Is that expected?
> Paul
> 
> elf/tst-glibc-hwcaps-prepend-cache.out:
> tst-glibc-hwcaps-prepend-cache.c:109: numeric comparison failure
>    left: 2 (0x2); from: marker1 ()
>   right: 3 (0x3); from: 3
> error: tst-glibc-hwcaps-prepend-cache.c:118: not true: dlopen (SONAME, RTLD_NOW) == NULL
> error: 2 test failures
> running post-clean rsync
> 
> stdio-common/tst-vfprintf-width-prec-mem.out:
> Memory not freed:
> -----------------
>    Address     Size     Caller
> 0xb09ea008 0x31fff9c  at 0xb6e242d4
> 0xb3bea008 0x18fff9c  at 0xb6e242d4
> 

  reply	other threads:[~2021-05-18 11:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 11:03 Paul Zimmermann
2021-05-18 11:11 ` Szabolcs Nagy [this message]
2021-05-18 13:51   ` Adhemerval Zanella

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=20210518111117.GR9028@arm.com \
    --to=szabolcs.nagy@arm.com \
    --cc=Paul.Zimmermann@inria.fr \
    --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).