public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pheeck at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/114627] New: [14 Regression] undefined behavior in tree-profile.cc while compiling gcc.misc-tests/gcov-18.c Date: Sun, 07 Apr 2024 09:43:38 +0000 [thread overview] Message-ID: <bug-114627-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114627 Bug ID: 114627 Summary: [14 Regression] undefined behavior in tree-profile.cc while compiling gcc.misc-tests/gcov-18.c Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: testsuite-fail Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: pheeck at gcc dot gnu.org Blocks: 63426 Target Milestone: --- Host: x86_64-pc-linux-gnu Target: x86_64-pc-linux-gnu Compiling gcc.misc-tests/gcov-19.c using ubsan-instrumented GCC gcc testsuite/gcc.misc-tests/gcov-19.c -fdiagnostics-plain-output -fcondition-coverage -ftest-coverage -lm -o ./gcov-19.exe results in /home/worker/buildworker/tiber-gcc-ubsan/build/gcc/tree-profile.cc:1090:48: runtime error: shift exponent 64 is too large for 64-bit type 'long long unsigned int' Compiler configured with --enable-languages=default,jit,lto,go,d --enable-host-shared --enable-checking=release --disable-multilib --with-build-config=bootstrap-ubsan Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426 [Bug 63426] [meta-bug] Issues found with -fsanitize=undefined
next reply other threads:[~2024-04-07 9:43 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-07 9:43 pheeck at gcc dot gnu.org [this message] 2024-04-07 9:43 ` [Bug middle-end/114627] " pheeck at gcc dot gnu.org 2024-04-08 8:45 ` [Bug middle-end/114627] " rguenth at gcc dot gnu.org 2024-04-09 7:58 ` cvs-commit 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-114627-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).