From: Joseph Myers <joseph@codesourcery.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>,
libc-alpha@sourceware.org
Subject: Re: [PATCH 2/2] powerpc: Move cache line size to rtld_global_ro
Date: Fri, 31 Jul 2020 18:35:54 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2007311833182.6115@digraph.polyomino.org.uk> (raw)
In-Reply-To: <874kpndfe4.fsf@oldenburg2.str.redhat.com>
On Fri, 31 Jul 2020, Florian Weimer via Libc-alpha wrote:
> * Joseph Myers:
>
> > I'm seeing all the statically linked glibc tests fail for 32-bit powerpc
> > when built with GCC 10:
> >
> > malloc.c:2394: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.
> > Aborted
> >
> > (A statically linked program with empty main produces that error on
> > startup.)
> >
> > If I build glibc with -fcommon, at least a trivial statically linked
> > binary no longer fails. So I think there may have been something missing
> > from the fixes to build with -fno-common; they got glibc building again,
> > but not working in the statically linked case.
>
> What's your binutils version?
This testing was with 2.35.50.20200720.
> Does this affect the statically linked test binaries built by
> build-many-glibcs.py?
Yes. I tested build-many-glibcs.py for powerpc-linux-gnu with current
default versions of everything (so binutils 2.35 branch in this case);
running the math/atest-exp binary left from a --keep=all build produces
that same assertion failure.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-07-31 18:36 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 1:19 powerpc build failure with GCC mainline -fno-common change Joseph Myers
2019-11-21 9:23 ` Andreas Schwab
2019-12-23 18:45 ` [PATCH] powerpc: Move cache line size to rtld_global_ro Tulio Magno Quites Machado Filho
2019-12-26 17:04 ` Adhemerval Zanella
2019-12-27 15:42 ` Tulio Magno Quites Machado Filho
2019-12-27 16:47 ` Adhemerval Zanella
2020-01-09 10:29 ` Florian Weimer
2020-01-09 16:43 ` Jeff Law
2020-01-09 17:20 ` Tulio Magno Quites Machado Filho
2020-01-09 18:03 ` Adhemerval Zanella
2020-01-09 18:49 ` Tulio Magno Quites Machado Filho
2020-01-09 18:54 ` Adhemerval Zanella
2020-01-10 22:27 ` [PATCH 1/2] powerpc: Initialize rtld_global_ro for static dlopen [BZ #20802] Tulio Magno Quites Machado Filho
2020-01-10 22:27 ` [PATCH 2/2] powerpc: Move cache line size to rtld_global_ro Tulio Magno Quites Machado Filho
2020-01-16 16:37 ` Carlos O'Donell
2020-01-17 3:56 ` Siddhesh Poyarekar
2020-01-17 12:39 ` Tulio Magno Quites Machado Filho
2020-01-17 17:14 ` Florian Weimer
2020-01-17 17:15 ` Joseph Myers
2020-01-17 22:28 ` Tulio Magno Quites Machado Filho
2020-01-17 23:45 ` [PATCH] powerpc32: Fix syntax error in __GLRO macro Andreas Schwab
2020-01-17 23:56 ` Tulio Magno Quites Machado Filho
2020-07-23 14:47 ` [PATCH 2/2] powerpc: Move cache line size to rtld_global_ro Joseph Myers
2020-07-23 16:46 ` Andreas Schwab
2020-07-31 12:42 ` Florian Weimer via Libc-alpha
2020-07-31 18:35 ` Joseph Myers [this message]
2020-08-03 8:15 ` Florian Weimer via Libc-alpha
2020-08-03 16:07 ` Carlos O'Donell via Libc-alpha
2020-01-16 16:21 ` [PATCH 1/2] powerpc: Initialize rtld_global_ro for static dlopen [BZ #20802] Carlos O'Donell
2020-01-16 16:25 ` Siddhesh Poyarekar
2020-01-09 18:56 ` [PATCH] powerpc: Move cache line size to rtld_global_ro Tulio Magno Quites Machado Filho
2020-01-10 9:38 ` Florian Weimer
2020-01-10 16:09 ` Shawn Landden
2020-01-10 18:19 ` Adhemerval Zanella
2019-11-22 16:58 ` powerpc build failure with GCC mainline -fno-common change Tulio Magno Quites Machado Filho
2019-11-23 13:23 ` Florian Weimer
2019-11-26 13:26 ` Tulio Magno Quites Machado Filho
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.2007311833182.6115@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=tuliom@linux.ibm.com \
/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).