From: Xi Ruoyao <xry111@xry111.site>
To: "Cristian Rodríguez" <crrodriguez@opensuse.org>,
"Adhemerval Zanella Netto" <adhemerval.zanella@linaro.org>
Cc: DJ Delorie <dj@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH v5 1/1] memalign: Support scanning for aligned chunks.
Date: Thu, 13 Apr 2023 01:04:13 +0800 [thread overview]
Message-ID: <e222a231f5684cfa2680e500d5579c7d878a6208.camel@xry111.site> (raw)
In-Reply-To: <CAPBLoAfJVKqXKe00A7dW-yDYrX+osDEe++b08gGd1jtLrRJSiA@mail.gmail.com>
On Thu, 2023-03-30 at 18:43 -0300, Cristian Rodríguez via Libc-alpha
wrote:
> On Thu, Mar 30, 2023 at 7:50 AM Adhemerval Zanella Netto <
> adhemerval.zanella@linaro.org> wrote:
>
> > Do you have any testcase that triggers it?
>
> I'll try.. cannot compile ripgrep with debug info either ..because this
> commit also makes rustc crash with the same message.😕
On LoongArch (with a GCC 12.2 but LoongArch backend patched to match GCC
trunk), this causes an almost deterministic failure of malloc/tst-
malloc-thread-fail-malloc-hugetlb2:
FAIL: malloc/tst-malloc-thread-fail-malloc-hugetlb2
original exit status 1
error: exit status 139 from child process
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2023-04-12 17:04 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 3:58 [PATCH v1 " DJ Delorie
2022-07-19 2:54 ` Carlos O'Donell
2022-07-19 3:57 ` [PATCH v2 " DJ Delorie
2022-07-19 9:19 ` Florian Weimer
2022-07-19 17:32 ` DJ Delorie
2022-07-20 0:32 ` [PATCH v3 " DJ Delorie
2022-07-22 20:21 ` DJ Delorie
2022-07-22 20:28 ` Joseph Myers
2022-07-28 19:50 ` [PATCH v4 " DJ Delorie
2022-08-17 19:00 ` DJ Delorie
2022-11-10 21:40 ` Ping^2: " DJ Delorie
2023-03-20 21:49 ` Ping^3: " DJ Delorie
2023-03-28 19:07 ` Adhemerval Zanella Netto
2023-03-29 4:20 ` [PATCH v5 " DJ Delorie
2023-03-29 19:41 ` Adhemerval Zanella Netto
2023-03-29 20:36 ` DJ Delorie
2023-03-30 10:04 ` Cristian Rodríguez
2023-03-30 10:50 ` Adhemerval Zanella Netto
2023-03-30 21:43 ` Cristian Rodríguez
2023-04-12 17:04 ` Xi Ruoyao [this message]
2023-04-12 17:16 ` DJ Delorie
2023-04-12 17:26 ` Xi Ruoyao
2023-04-13 1:52 ` [PATCH v6 " DJ Delorie
2023-04-13 5:51 ` Xi Ruoyao
2023-04-17 21:48 ` Carlos O'Donell
2023-04-18 1:25 ` [PATCH v7] " DJ Delorie
2023-04-18 13:58 ` Carlos O'Donell
2023-04-18 15:02 ` DJ Delorie
2023-04-12 17:33 ` [PATCH v5 1/1] " Adhemerval Zanella Netto
2023-04-12 17:40 ` DJ Delorie
2023-04-12 18:01 ` Adhemerval Zanella Netto
2023-04-13 1:57 ` DJ Delorie
2023-04-13 10:46 ` Adhemerval Zanella Netto
2023-04-05 14:07 ` Stefan Liebler
2023-04-05 17:58 ` DJ Delorie
2023-04-11 11:40 ` Stefan Liebler
2023-04-12 11:23 ` Stefan Liebler
2023-03-31 15:39 ` Adhemerval Zanella Netto
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=e222a231f5684cfa2680e500d5579c7d878a6208.camel@xry111.site \
--to=xry111@xry111.site \
--cc=adhemerval.zanella@linaro.org \
--cc=crrodriguez@opensuse.org \
--cc=dj@redhat.com \
--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).