public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bouanto at zoho dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/100242] New: libgccjit.so: error: in expmed_mode_index, at expmed.h:249
Date: Sat, 24 Apr 2021 00:33:09 +0000	[thread overview]
Message-ID: <bug-100242-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100242

            Bug ID: 100242
           Summary: libgccjit.so: error: in expmed_mode_index, at
                    expmed.h:249
           Product: gcc
           Version: 10.3.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: jit
          Assignee: dmalcolm at gcc dot gnu.org
          Reporter: bouanto at zoho dot com
  Target Milestone: ---

Created attachment 50664
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50664&action=edit
First part of the compressed reproducer

Hi.
I get the following error for the attached reproducer:

during RTL pass: expand
libgccjit.so: error: in expmed_mode_index, at expmed.h:249
0x7f0da2e61a35 expmed_mode_index
        ../../../gcc/gcc/expmed.h:249
0x7f0da2e61aa4 expmed_op_cost_ptr
        ../../../gcc/gcc/expmed.h:271
0x7f0da2e620dc sdiv_cost_ptr
        ../../../gcc/gcc/expmed.h:540
0x7f0da2e62129 sdiv_cost
        ../../../gcc/gcc/expmed.h:558
0x7f0da2e73c12 expand_divmod(int, tree_code, machine_mode, rtx_def*, rtx_def*,
rtx_def*, int)
        ../../../gcc/gcc/expmed.c:4335
0x7f0da2ea1423 expand_expr_real_2(separate_ops*, rtx_def*, machine_mode,
expand_modifier)
        ../../../gcc/gcc/expr.c:9240
0x7f0da2cd1a1e expand_gimple_stmt_1
        ../../../gcc/gcc/cfgexpand.c:3796
0x7f0da2cd1c30 expand_gimple_stmt
        ../../../gcc/gcc/cfgexpand.c:3857
0x7f0da2cd90a9 expand_gimple_basic_block
        ../../../gcc/gcc/cfgexpand.c:5898
0x7f0da2cdade8 execute
        ../../../gcc/gcc/cfgexpand.c:6582

The reproducer was so big that I needed to compress it and split it in 3 files,
so you'll have to cat the 3 files together and uncompress it.

(If you could also explain to me how to find out where exactly is the issue in
the reproducer in order to make it smaller and easier to debug, I'd
appreciate.)

Thanks to fix this issue.

             reply	other threads:[~2021-04-24  0:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-24  0:33 bouanto at zoho dot com [this message]
2021-04-24  0:33 ` [Bug jit/100242] " bouanto at zoho dot com
2021-04-24  0:34 ` bouanto at zoho dot com
2021-04-24 16:14 ` bouanto at zoho dot com
2021-05-11 12:22 ` marxin at gcc dot gnu.org
2021-08-16 11:37 ` marxin 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-100242-4@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).