public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/106459] New: Compiler crashing for loongarch64-linux-gnu on windows
Date: Wed, 27 Jul 2022 23:12:45 +0000 [thread overview]
Message-ID: <bug-106459-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106459
Bug ID: 106459
Summary: Compiler crashing for loongarch64-linux-gnu on windows
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: unlvsur at live dot com
Target Milestone: ---
Created attachment 53367
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53367&action=edit
preprocessor file
D:\hg\fast_io\.sha512>loongarch64-linux-gnu-g++ -S sha512.cc -Ofast -std=c++23
-I../include
In file included from ../include/fast_io_crypto/hash/sha512.h:183,
from ../include/fast_io_crypto/hash/impl.h:6,
from ../include/fast_io_crypto.h:25,
from sha512.cc:1:
../include/fast_io_crypto/hash/sha512_scalar.h: In function 'void
fast_io::details::sha512::sha512_runtime_routine(uint_least64_t*, const
std::byte*, const std::byte*)':
../include/fast_io_crypto/hash/sha512_scalar.h:99:1: error: unrecognizable
insn:
99 | }
| ^
(insn 30 29 31 4 (set (reg:DI 1071)
(ior:DI (zero_extend:DI (subreg:SI (reg:DI 1071) 0))
(const_int 2867079648641024 [0xa2f9800000000])))
"../include/fast_io_crypto/hash/sha512.h":90:5 -1
(nil))
during RTL pass: vregs
../include/fast_io_crypto/hash/sha512_scalar.h:99:1: internal compiler error:
in extract_insn, at recog.cc:2791
libbacktrace could not find executable to open
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
See <https://gcc.gnu.org/bugs/> for instructions.
D:\hg\fast_io\.sha512>loongarch64-linux-gnu-g++ -S sha512.cc -Ofast -std=c++23
-I../include -freport-bug
In file included from ../include/fast_io_crypto/hash/sha512.h:183,
from ../include/fast_io_crypto/hash/impl.h:6,
from ../include/fast_io_crypto.h:25,
from sha512.cc:1:
../include/fast_io_crypto/hash/sha512_scalar.h: In function 'void
fast_io::details::sha512::sha512_runtime_routine(uint_least64_t*, const
std::byte*, const std::byte*)':
../include/fast_io_crypto/hash/sha512_scalar.h:99:1: error: unrecognizable
insn:
99 | }
| ^
(insn 30 29 31 4 (set (reg:DI 1071)
(ior:DI (zero_extend:DI (subreg:SI (reg:DI 1071) 0))
(const_int 2867079648641024 [0xa2f9800000000])))
"../include/fast_io_crypto/hash/sha512.h":90:5 -1
(nil))
during RTL pass: vregs
../include/fast_io_crypto/hash/sha512_scalar.h:99:1: internal compiler error:
in extract_insn, at recog.cc:2791
libbacktrace could not find executable to open
Please submit a full bug report, with preprocessed source.
See <https://gcc.gnu.org/bugs/> for instructions.
loongarch64-linux-gnu-g++: fatal error: cannot execute
'd:/x86_64-windows-gnu/loongarch64-linux-gnu/bin/../libexec/gcc/loongarch64-linux-gnu/13.0.0/cc1plus.exe':
open temporary output file
compilation terminated.
next reply other threads:[~2022-07-27 23:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 23:12 unlvsur at live dot com [this message]
2022-07-27 23:15 ` [Bug other/106459] " unlvsur at live dot com
2022-07-27 23:17 ` [Bug c++/106459] " unlvsur at live dot com
2022-07-27 23:23 ` [Bug target/106459] " pinskia at gcc dot gnu.org
2022-07-27 23:40 ` pinskia at gcc dot gnu.org
2022-07-27 23:42 ` pinskia at gcc dot gnu.org
2022-08-24 7:50 ` paul.hua.gm at gmail dot com
2022-08-25 1:19 ` cvs-commit at gcc dot gnu.org
2022-08-25 1:42 ` cvs-commit at gcc dot gnu.org
2023-01-08 7:48 ` pinskia 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-106459-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).