public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/110859] New FAIL: 23_containers/vector/bool/110807.cc Date: Sat, 07 Oct 2023 18:13:30 +0000 [thread overview] Message-ID: <bug-110859-4-KcHyYrBdeK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110859-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110859 --- Comment #3 from John David Anglin <danglin at gcc dot gnu.org> --- FAIL: 23_containers/vector/bool/110807.cc -std=gnu++17 (test for excess errors) Excess errors: /home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/include/bits/stl_algobase.h:440: warning: 'void* __builtin_memmove(void*, const void*, unsigned int)' writing between 5 and 268435455 bytes into a region of size 4 overflows the destination [-Wstringop-overflow=]
next prev parent reply other threads:[~2023-10-07 18:13 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-31 14:44 [Bug libstdc++/110859] New: [14 Regression] " carlos.seo at linaro dot org 2023-07-31 21:07 ` [Bug libstdc++/110859] " pinskia at gcc dot gnu.org 2023-07-31 21:09 ` [Bug middle-end/110859] " pinskia at gcc dot gnu.org 2023-10-07 18:13 ` danglin at gcc dot gnu.org [this message] 2023-11-06 12:39 ` redi at gcc dot gnu.org 2023-11-11 1:00 ` redi 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-110859-4-KcHyYrBdeK@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).