public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: Antoni Boucher <bouanto@zoho.com>
To: David Malcolm <dmalcolm@redhat.com>,
	jit@gcc.gnu.org,  gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libgccjit: Fix GGC segfault when using -flto
Date: Mon, 11 Dec 2023 19:20:03 -0500	[thread overview]
Message-ID: <f400de72914ea95932e14fe40eb1f79a6c3a83f7.camel@zoho.com> (raw)
In-Reply-To: <9738ef0c44d5f5505607c6678d23683aaba2c72f.camel@redhat.com>

I'm not sure how to do this. I tried the following commands, but this
fails even on master:

../../gcc/configure --enable-host-shared --enable-
languages=c,jit,c++,fortran,objc,lto --enable-checking=release --
disable-werror --prefix=/opt/gcc

make bootstrap -j24
make -k check -j24

From what I can understand, the unexpected failures are in g++:

		=== g++ Summary ===

# of expected passes		72790
# of unexpected failures	1
# of expected failures		1011
# of unsupported tests		3503

		=== g++ Summary ===

# of expected passes		4750
# of unexpected failures	27
# of expected failures		16
# of unsupported tests		43


Am I doing something wrong?

On Fri, 2023-12-01 at 12:49 -0500, David Malcolm wrote:
> On Thu, 2023-11-30 at 17:13 -0500, Antoni Boucher wrote:
> > Here's the updated patch.
> > The failure was due to the test being in the test array while it
> > should
> > not have been there since it changes the context.
> 
> Thanks for the updated patch.
> 
> Did you do a full bootstrap and regression test with this one, or do
> you want me to?
> 
> Dave
> 


  reply	other threads:[~2023-12-12  0:20 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
2023-11-30 22:13     ` Antoni Boucher
2023-12-01 17:49       ` David Malcolm
2023-12-12  0:20         ` Antoni Boucher [this message]
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=f400de72914ea95932e14fe40eb1f79a6c3a83f7.camel@zoho.com \
    --to=bouanto@zoho.com \
    --cc=dmalcolm@redhat.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).