From: David Malcolm <dmalcolm@redhat.com>
To: Antoni Boucher <bouanto@zoho.com>,
jit@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libgccjit: Fix GGC segfault when using -flto
Date: Sun, 12 Nov 2023 18:03:02 -0500 [thread overview]
Message-ID: <d186c01e8d88bc3ce73d731c156a1035535078d0.camel@redhat.com> (raw)
In-Reply-To: <459954b377768b7a0d79dd9d99328b45c66e4fa0.camel@redhat.com>
On Fri, 2023-11-10 at 18:14 -0500, David Malcolm wrote:
> On Fri, 2023-11-10 at 11:02 -0500, Antoni Boucher wrote:
> > Hi.
> > This patch fixes the segfault when using -flto with libgccjit (bug
> > 111396).
> >
> > You mentioned in bugzilla that this didn't fix the reproducer for
> > you,
>
> Rereading https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111396 it
> looks
> like all I tested back in August was your reproducer; I didn't yet
> test
> your patch.
>
> > but it does for me.
> > At first, the test case would not pass, but running "make install"
> > made
> > it pass.
> > Not sure if this is normal.
> >
> > Could you please check if this fixes the issue on your side as
> > well?
> > Since this patch changes files outside of gcc/jit, what tests
> > should
> > I
> > run to make sure it didn't break anything?
>
> I'm trying your patch in my tester now.
Bootstrapped with x86_64-pc-linux-gnu/build. No changes to non-jit
tests, but had this effect on jit.sum:
Changes to jit.sum
------------------
FAIL: 9->11 (+2)
PASS: 14827->11434 (-3393)
apparently due to:
FAIL: test-combination.c.exe iteration 1 of 5: verify_code_accessing_bitfield: result is NULL
FAIL: test-combination.c.exe killed: 997638 exp16 0 0 CHILDKILLED SIGABRT SIGABRT
>
> BTW, we shouldn't add test-ggc-bugfix to since it adds options to the
> context: this would affect all the other tests.
next prev parent reply other threads:[~2023-11-12 23:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 16:02 Antoni Boucher
2023-11-10 23:14 ` David Malcolm
2023-11-12 23:03 ` David Malcolm [this message]
2023-11-30 22:13 ` Antoni Boucher
2023-12-01 17:49 ` David Malcolm
2023-12-12 0:20 ` Antoni Boucher
2024-01-10 15:19 ` David Malcolm
2024-01-10 15:27 ` Antoni Boucher
2024-01-10 22:20 ` David Malcolm
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=d186c01e8d88bc3ce73d731c156a1035535078d0.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=bouanto@zoho.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jit@gcc.gnu.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).