public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/95521] libgccjit.so: error: in build2, at tree.c:4743
Date: Thu, 04 Jun 2020 14:00:13 +0000 [thread overview]
Message-ID: <bug-95521-4-KsBc8tWdWx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95521-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95521
--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to bouanto from comment #0)
> The reproducer is very big, so tell me if you want me to try to make it
> smaller.
Yes please!
The attachment reproduces the ICE for me, but is too big for me to work with.
By adding this:
gcc_jit_context_dump_to_file (ctxt_0x7feee9512e00, "/tmp/something.c",
1 /* update_locations */);
to immediately after the create call code, it generates "source" locations in
the generated /tmp/something.c. By poking in the debugger at the location
info:
(gdb) p loc->m_recording_loc->m_line
$10 = 6773
it shows that the issue is triggered at line 6773, which is here in the dump:
repeat_loop_body:
*((unsigned char *)loop_var) = returnValue;
intLocal = (unsigned long long)1;
loop_var += *((unsigned char * *)&intLocal); <<<<< HERE
goto repeat_loop_header;
within extern bool
_ZN4core3fmt3num12GenericRadix7fmt_int17h0643c6b8b66acb3dE (struct
fmt::num::Binary * param, unsigned int param, struct fmt::Formatter * param)
Is it possible for you to use the above info to make a small(er) reproducer?
Thanks.
next prev parent reply other threads:[~2020-06-04 14:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 23:42 [Bug jit/95521] New: " bouanto at zoho dot com
2020-06-04 0:05 ` [Bug jit/95521] " pinskia at gcc dot gnu.org
2020-06-04 13:57 ` dmalcolm at gcc dot gnu.org
2020-06-04 14:00 ` dmalcolm at gcc dot gnu.org [this message]
2020-06-04 14:46 ` bouanto at zoho dot com
2020-06-04 15:09 ` dmalcolm at gcc dot gnu.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-95521-4-KsBc8tWdWx@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).