public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/101443] internal compiler error: in wide_int_to_tree_1, at tree.c:1519 Date: Tue, 13 Jul 2021 20:04:55 +0000 [thread overview] Message-ID: <bug-101443-4-cbYutSdG0u@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101443-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101443 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2021-07-13 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- #6 0x000000000085567e in wide_int_to_tree_1 (type=0x7ffff6cd9bd0, pcst=...) at /home/apinski/src/upstream-gcc-git/gcc/gcc/tree.c:1751 1751 gcc_unreachable (); (gdb) l 1746 1747 case ENUMERAL_TYPE: 1748 break; 1749 1750 default: 1751 gcc_unreachable (); 1752 } 1753 1754 if (ix >= 0) 1755 { (gdb) p type $1 = (tree) 0x7ffff6cd9bd0 (gdb) p debug_tree(type) <nullptr_type 0x7ffff6cd9bd0 decltype(nullptr) sizes-gimplified unsigned type_6 DI size <integer_cst 0x7ffff6b77ed0 type <integer_type 0x7ffff6b950a8 bitsizetype> constant 64> unit-size <integer_cst 0x7ffff6b77ee8 type <integer_type 0x7ffff6b95000 sizetype> constant 8> align:64 warn_if_not_align:0 symtab:0 alias-set 46 canonical-type 0x7ffff6cd9bd0 pointer_to_this <pointer_type 0x7ffff44910a8> reference_to_this <reference_type 0x7ffff448adc8>> nullptr_type seems a bit off here.
next prev parent reply other threads:[~2021-07-13 20:04 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-13 19:43 [Bug c++/101443] New: " rawiener at amazon dot com 2021-07-13 20:04 ` pinskia at gcc dot gnu.org [this message] 2021-07-13 20:29 ` [Bug c++/101443] " rawiener at amazon dot com 2021-07-13 21:07 ` pinskia at gcc dot gnu.org 2021-07-14 9:13 ` jakub at gcc dot gnu.org 2021-07-14 10:18 ` jakub at gcc dot gnu.org 2021-07-14 10:22 ` [Bug c++/101443] [9/10/11/12 Regression] " jakub at gcc dot gnu.org 2021-07-15 16:54 ` cvs-commit at gcc dot gnu.org 2021-07-15 16:55 ` [Bug c++/101443] [9/10/11 " jakub at gcc dot gnu.org 2021-07-18 23:29 ` cvs-commit at gcc dot gnu.org 2021-07-19 7:55 ` [Bug c++/101443] [9/10 " jakub at gcc dot gnu.org 2022-05-10 8:19 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:21 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:36 ` jakub at gcc dot gnu.org 2024-02-27 16:16 ` rawiener at amazon dot com
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-101443-4-cbYutSdG0u@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).