public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105975] New: OpenMP/nvptx offloading: 'internal compiler error: in maybe_legitimize_operand, at optabs.cc:7785'
Date: Tue, 14 Jun 2022 14:40:36 +0000	[thread overview]
Message-ID: <bug-105975-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105975
           Summary: OpenMP/nvptx offloading: 'internal compiler error: in
                    maybe_legitimize_operand, at optabs.cc:7785'
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: openmp
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: tschwinge at gcc dot gnu.org
                CC: jakub at gcc dot gnu.org, rsandifo at gcc dot gnu.org,
                    vries at gcc dot gnu.org
  Target Milestone: ---
            Target: nvptx

The recent commit r13-1068-g1d205dbac1e1754c01c22a31bd1688126545401e "Factor
out common internal-fn idiom" causes a class of ICEs in OpenMP/nvptx offloading
compilation: 'during RTL pass: expand', 'internal compiler error: in
maybe_legitimize_operand, at optabs.cc:7785', seen for a lot of libgomp
OpenMP/nvptx offloading test cases (with '-O1' and higher).

    0xb1b0b3 maybe_legitimize_operand
            [...]/source-gcc/gcc/optabs.cc:7785
    0xb1b0b3 maybe_legitimize_operands(insn_code, unsigned int, unsigned int,
expand_operand*)
            [...]/source-gcc/gcc/optabs.cc:7936
    0xb1b139 maybe_gen_insn(insn_code, unsigned int, expand_operand*)
            [...]/source-gcc/gcc/optabs.cc:7955
    0xb1a8b8 maybe_expand_insn(insn_code, unsigned int, expand_operand*)
            [...]/source-gcc/gcc/optabs.cc:7998
    0xb1a8b8 expand_insn(insn_code, unsigned int, expand_operand*)
            [...]/source-gcc/gcc/optabs.cc:8029
    0x95dcb3 expand_fn_using_insn
            [...]/source-gcc/gcc/internal-fn.cc:193
    0x6d3ee7 expand_call_stmt
            [...]/source-gcc/gcc/cfgexpand.cc:2737
    0x6d3ee7 expand_gimple_stmt_1
            [...]/source-gcc/gcc/cfgexpand.cc:3869

For extra entertainment: when running with '-wrapper "$GDB",-q,--args', we get
'[Inferior 1 (process [...]) exited normally]'...  (Maybe Valgrind could help? 
Unless someone directly pinpoints the issue, of course.)

I've not yet determined whether it's a latent problem just exposed by this
commit, or whether the commit itself has an issue.  It's not magically fixed by
the related subsequent commit
r13-1069-gf8baf4004ef965ce7a9edf6d2f5eb99adb15803a "Add a general mapping from
internal fns to target insns".

'gcc/internal-fn.cc':

    193    expand_insn (icode, opno, ops);

'gcc/optabs.cc':

    8026        expand_insn (enum insn_code icode, unsigned int nops,
    8027                     class expand_operand *ops)
    8028        {
    8029          if (!maybe_expand_insn (icode, nops, ops))

    7995        maybe_expand_insn (enum insn_code icode, unsigned int nops,
    7996                           class expand_operand *ops)
    7997        {
    7998          rtx_insn *pat = maybe_gen_insn (icode, nops, ops);

    7951        maybe_gen_insn (enum insn_code icode, unsigned int nops,
    7952                        class expand_operand *ops)
    7953        {
    7954          gcc_assert (nops == (unsigned int) insn_data[(int)
icode].n_generator_args);
    7955          if (!maybe_legitimize_operands (icode, 0, nops, ops))

    7935              /* Otherwise try legitimizing the operand on its own.  */
    7936              if (j == i && !maybe_legitimize_operand (icode, opno + i,
&ops[i]))

    7784            case EXPAND_OUTPUT:
    7785              gcc_assert (mode != VOIDmode);

             reply	other threads:[~2022-06-14 14:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 14:40 tschwinge at gcc dot gnu.org [this message]
2022-06-14 20:08 ` [Bug target/105975] " rsandifo at gcc dot gnu.org
2022-06-15  8:49 ` tschwinge at gcc dot gnu.org
2022-06-15  8:51 ` tschwinge at gcc dot gnu.org
2022-06-15 11:01 ` rsandifo at gcc dot gnu.org
2022-06-15 16:40 ` cvs-commit at gcc dot gnu.org
2022-06-15 16:42 ` rsandifo at gcc dot gnu.org
2022-06-15 21:04 ` tschwinge 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-105975-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).