public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107365] New: ICE in verify_range, at value-range.cc:726 Date: Sun, 23 Oct 2022 10:59:49 +0000 [thread overview] Message-ID: <bug-107365-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107365 Bug ID: 107365 Summary: ICE in verify_range, at value-range.cc:726 Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: marxin at gcc dot gnu.org CC: aldyh at gcc dot gnu.org Target Milestone: --- Host: x86_64-linux-gnu Target: vax-linux-gnu Happens for a cross compiler: $ ./xgcc -B./ -B/home/marxin/bin/gcc/vax-linux-gnu/bin/ -isystem /home/marxin/bin/gcc/vax-linux-gnu/include -isystem /home/marxin/bin/gcc/vax-linux-gnu/sys-include -L/dev/shm/objdir2/gcc/../ld -xc++ -nostdinc /dev/null -S -o /dev/null -fself-test=/home/marxin/Programming/gcc/gcc/testsuite/selftests In function ‘test_fn’: cc1plus: internal compiler error: in verify_range, at value-range.cc:726 0x18dbdc5 frange::verify_range() /home/marxin/Programming/gcc/gcc/value-range.cc:726 0x18da448 frange::set(tree_node*, real_value const&, real_value const&, value_range_kind) /home/marxin/Programming/gcc/gcc/value-range.cc:366 0x18f17fe frange::frange(tree_node*, real_value const&, real_value const&, value_range_kind) /home/marxin/Programming/gcc/gcc/value-range.h:1080 0x18ed069 frange_float /home/marxin/Programming/gcc/gcc/value-range.cc:3692 0x18f021c range_tests_floats /home/marxin/Programming/gcc/gcc/value-range.cc:3959 0x18f11c9 selftest::range_tests() /home/marxin/Programming/gcc/gcc/value-range.cc:4052 0x20549b7 test_ranges /home/marxin/Programming/gcc/gcc/function-tests.cc:584 0x20549b7 selftest::function_tests_cc_tests() /home/marxin/Programming/gcc/gcc/function-tests.cc:680 0x21b488c selftest::run_tests() /home/marxin/Programming/gcc/gcc/selftest-run-tests.cc:107 0x146880e toplev::run_self_tests() /home/marxin/Programming/gcc/gcc/toplev.cc:2184 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.
next reply other threads:[~2022-10-23 10:59 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-23 10:59 marxin at gcc dot gnu.org [this message] 2022-10-23 11:00 ` [Bug tree-optimization/107365] " marxin at gcc dot gnu.org 2022-10-23 14:54 ` aldyh at gcc dot gnu.org 2022-10-23 14:54 ` aldyh at gcc dot gnu.org 2022-10-24 10:16 ` cvs-commit at gcc dot gnu.org 2022-10-24 10:20 ` aldyh 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-107365-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: linkBe 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).