public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/115203] New: [15 Regression] Build fail with non LANG=C in analyzer self test: ICE in fail_formatted at selftest.cc:63 / tree-diagnostic-path.cc:2158: test_control_flow_5: FAIL: ASSERT_STREQ Date: Thu, 23 May 2024 11:04:25 +0000 [thread overview] Message-ID: <bug-115203-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115203 Bug ID: 115203 Summary: [15 Regression] Build fail with non LANG=C in analyzer self test: ICE in fail_formatted at selftest.cc:63 / tree-diagnostic-path.cc:2158: test_control_flow_5: FAIL: ASSERT_STREQ Product: gcc Version: 15.0 Status: UNCONFIRMED Keywords: build, ice-on-valid-code Severity: normal Priority: P3 Component: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org Target Milestone: --- For some testing, I happened to build with LANG=de_DE.UTF-8 and that was also set when building GCC itself. That works fine until the analyzer self test - as the strings don't match: .../build-gcc-trunk-fast/./gcc/xgcc -B/home/tob/projects/build-gcc-trunk-fast/./gcc/ -xc++ -nostdinc /dev/null -S -o /dev/null -fself-test=.../gcc/testsuite/selftests .../gcc/tree-diagnostic-path.cc:2158: test_control_flow_5: FAIL: ASSERT_STREQ (" events 1-5\n" "FILENAME:1:6:\n" " 1 | if ((arr = (struct foo **)malloc [...] 5 || if ((arr[i] = (struct foo *)malloc(sizeof(struct foo))) == NULL) { || ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~ || | | |+----------->(4) ...to here (5) wurde hier deklariert cc1plus: interner Compiler-Fehler: in fail_formatted, bei selftest.cc:63 0x22af256 selftest::fail_formatted(selftest::location const&, char const*, ...) ../../../repos/gcc/gcc/selftest.cc:63 0x22af301 selftest::assert_streq(selftest::location const&, char const*, char const*, char const*, char const*) ../../../repos/gcc/gcc/selftest.cc:92 0x25b6cd6 selftest::fail_formatted(selftest::location const&, char const*, ...) ../../../repos/gcc/gcc/selftest.cc:63 0x25b6d81 selftest::assert_streq(selftest::location const&, char const*, char const*, char const*, char const*) ../../../repos/gcc/gcc/selftest.cc:92 0x10a7b42 test_control_flow_5 ../../../repos/gcc/gcc/tree-diagnostic-path.cc:2158 0x10aabe6 control_flow_tests ../../../repos/gcc/gcc/tree-diagnostic-path.cc:2292 0x13a5512 test_control_flow_5 ../../../repos/gcc/gcc/tree-diagnostic-path.cc:2158 0x13a85b6 control_flow_tests ../../../repos/gcc/gcc/tree-diagnostic-path.cc:2292
next reply other threads:[~2024-05-23 11:04 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-23 11:04 burnus at gcc dot gnu.org [this message] 2024-05-23 12:41 ` [Bug analyzer/115203] " rguenth at gcc dot gnu.org 2024-05-23 13:39 ` dmalcolm at gcc dot gnu.org 2024-05-23 13:49 ` burnus at gcc dot gnu.org 2024-05-23 14:11 ` dmalcolm at gcc dot gnu.org 2024-05-28 17:08 ` cvs-commit at gcc dot gnu.org 2024-05-28 17:14 ` dmalcolm 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-115203-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).