public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "simon.chopin at canonical dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug malloc/31553] elf/tst-decorate-maps fails on ppc64el Date: Mon, 25 Mar 2024 18:17:49 +0000 [thread overview] Message-ID: <bug-31553-131-77s6g2YD6b@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31553-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31553 Simon Chopin <simon.chopin at canonical dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |minor --- Comment #3 from Simon Chopin <simon.chopin at canonical dot com> --- Thanks Andreas for pointing me to the page size. There's an assumption made in the test that the early allocation code will need to grow beyond the initial data page, as those extra pages would be the ones marked "[anon: glibc: loader malloc]". However, if the page size is large enough, I guess that assumption isn't valid anymore. I'll write a patch skipping this particular assertion if the page size is 64k or above. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-25 18:17 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-25 13:19 [Bug malloc/31553] New: " simon.chopin at canonical dot com 2024-03-25 13:27 ` [Bug malloc/31553] " schwab@linux-m68k.org 2024-03-25 14:02 ` simon.chopin at canonical dot com 2024-03-25 18:17 ` simon.chopin at canonical dot com [this message] 2024-03-26 13:39 ` adhemerval.zanella at linaro dot org 2024-04-22 18:40 ` adhemerval.zanella at linaro dot org
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=bug-31553-131-77s6g2YD6b@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: linkBe 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).