public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104448] New: [10/11/12 Regression] ICE: in initialize, at function-abi.cc:108 with -mavx5124vnniw / -mavx5124fmaps -mno-xsave -mabi=ms
Date: Tue, 08 Feb 2022 19:46:47 +0000	[thread overview]
Message-ID: <bug-104448-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104448
           Summary: [10/11/12 Regression] ICE: in initialize, at
                    function-abi.cc:108 with -mavx5124vnniw /
                    -mavx5124fmaps -mno-xsave -mabi=ms
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zsojka at seznam dot cz
  Target Milestone: ---
              Host: x86_64-pc-linux-gnu
            Target: x86_64-pc-linux-gnu

Compiler output: (empty source file)
$ echo > testcase.c
$ x86_64-pc-linux-gnu-gcc -mavx5124vnniw -mno-xsave -mabi=ms testcase.c 
testcase.c: internal compiler error: in initialize, at function-abi.cc:108
0x6dff4d predefined_function_abi::initialize(unsigned int, HARD_REG_SET const&)
        /repo/gcc-trunk/gcc/function-abi.cc:108
0xcf5695 backend_init
        /repo/gcc-trunk/gcc/toplev.cc:1785
0xcf5695 do_compile
        /repo/gcc-trunk/gcc/toplev.cc:2140
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
$ x86_64-pc-linux-gnu-gcc -mavx5124fmaps -mno-xsave -mabi=ms testcase.c 
testcase.c: internal compiler error: in initialize, at function-abi.cc:108
0x6dff4d predefined_function_abi::initialize(unsigned int, HARD_REG_SET const&)
        /repo/gcc-trunk/gcc/function-abi.cc:108
0xcf5695 backend_init
        /repo/gcc-trunk/gcc/toplev.cc:1785
0xcf5695 do_compile
        /repo/gcc-trunk/gcc/toplev.cc:2140
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

$ x86_64-pc-linux-gnu-gcc -v
Using built-in specs.
COLLECT_GCC=/repo/gcc-trunk/binary-latest-amd64/bin/x86_64-pc-linux-gnu-gcc
COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r12-7089-20220208123931-g0103c2e4082-checking-yes-rtl-df-extra-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/12.0.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++
--enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra
--with-cloog --with-ppl --with-isl --build=x86_64-pc-linux-gnu
--host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu
--with-ld=/usr/bin/x86_64-pc-linux-gnu-ld
--with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r12-7089-20220208123931-g0103c2e4082-checking-yes-rtl-df-extra-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.0.1 20220208 (experimental) (GCC)

             reply	other threads:[~2022-02-08 19:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 19:46 zsojka at seznam dot cz [this message]
2022-02-09  7:37 ` [Bug target/104448] " rguenth at gcc dot gnu.org
2022-02-16 15:50 ` jakub at gcc dot gnu.org
2022-02-16 15:54 ` ubizjak at gmail dot com
2022-02-16 16:04 ` cvs-commit at gcc dot gnu.org
2022-02-16 16:07 ` jakub at gcc dot gnu.org
2022-02-19  8:03 ` cvs-commit 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-104448-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).