public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95768] [11 Regression] -march=sandybridge -O2 -Wall crashes as 'during GIMPLE pass: uninit ... Segmentation fault' Date: Mon, 22 Jun 2020 15:13:36 +0000 [thread overview] Message-ID: <bug-95768-4-jEIg5drDBX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95768-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95768 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=95580 --- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> --- In fact, the same test case as for pr95580 triggers the C++ ICE as well: $ gcc -O1 -S -Wall -fno-tree-dce -xc++ /src/gcc/trunk/gcc/testsuite/gcc.dg/pr95580.c ‘ during GIMPLE pass: uninit In function ‘void foo(int)’: Segmentation fault 8 | foo (int x) | ^~~ 0x15c3040 crash_signal /src/gcc/trunk/gcc/toplev.c:328 0x9559fc location_wrapper_p(tree_node const*) /src/gcc/trunk/gcc/tree.h:4004 0x955a79 tree_strip_any_location_wrapper(tree_node*) /src/gcc/trunk/gcc/tree.h:4016 0x1a04ede integer_onep(tree_node const*) /src/gcc/trunk/gcc/tree.c:2573 0xa9878e dump_expr /src/gcc/trunk/gcc/cp/error.c:2386 0xa9b4f4 expr_to_string(tree_node*) /src/gcc/trunk/gcc/cp/error.c:3109 0xa9f1e7 cp_printer /src/gcc/trunk/gcc/cp/error.c:4264 0x270616b pp_format(pretty_printer*, text_info*) /src/gcc/trunk/gcc/pretty-print.c:1475 0x26df21d diagnostic_report_diagnostic(diagnostic_context*, diagnostic_info*) /src/gcc/trunk/gcc/diagnostic.c:1159 0x26df841 diagnostic_impl /src/gcc/trunk/gcc/diagnostic.c:1309 0x26e00bd warning_at(unsigned int, int, char const*, ...) /src/gcc/trunk/gcc/diagnostic.c:1446 0x1915da3 maybe_warn_operand /src/gcc/trunk/gcc/tree-ssa-uninit.c:431 0x1916782 warn_uninitialized_vars /src/gcc/trunk/gcc/tree-ssa-uninit.c:640 0x191b3e7 execute /src/gcc/trunk/gcc/tree-ssa-uninit.c:2936 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions.
next prev parent reply other threads:[~2020-06-22 15:13 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-19 15:10 [Bug c++/95768] New: " slyfox at inbox dot ru 2020-06-19 15:11 ` [Bug c++/95768] " slyfox at inbox dot ru 2020-06-19 19:49 ` hjl.tools at gmail dot com 2020-06-22 7:30 ` [Bug tree-optimization/95768] [11 Regression] " rguenth at gcc dot gnu.org 2020-06-22 15:02 ` [Bug c++/95768] " msebor at gcc dot gnu.org 2020-06-22 15:13 ` msebor at gcc dot gnu.org [this message] 2020-06-23 14:47 ` msebor at gcc dot gnu.org 2020-12-11 10:24 ` marxin at gcc dot gnu.org 2020-12-11 16:04 ` msebor at gcc dot gnu.org 2021-01-02 22:23 ` msebor at gcc dot gnu.org 2021-01-06 20:46 ` cvs-commit at gcc dot gnu.org 2021-01-06 20:48 ` msebor 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-95768-4-jEIg5drDBX@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).