public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/97392] [11 regression] g++.dg/asan/asan_test.C compilation failure starting with r11-3827 Date: Thu, 05 Nov 2020 10:30:55 +0000 [thread overview] Message-ID: <bug-97392-4-klXf4Rea2O@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97392-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97392 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-9 branch has been updated by Martin Liska <marxin@gcc.gnu.org>: https://gcc.gnu.org/g:82972dc3ec83b88280a830540e8127e2a45d61f0 commit r9-9025-g82972dc3ec83b88280a830540e8127e2a45d61f0 Author: Martin Liska <mliska@suse.cz> Date: Tue Oct 13 10:09:47 2020 +0200 ASAN: disable -Wno-stringop-overflow for 2 tests gcc/testsuite/ChangeLog: PR middle-end/97392 * g++.dg/asan/asan_test.C: Disable -Wstringop-overflow. * gcc.dg/asan/pr80166.c: Likewise. (cherry picked from commit 8e0e9417ccda583a1bf05ff08e86fdffbec62b3e) (cherry picked from commit a79cb813205027576d47a27655198cec4b5cd046)
prev parent reply other threads:[~2020-11-05 10:30 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-12 22:46 [Bug middle-end/97392] New: " seurer at gcc dot gnu.org 2020-10-13 6:25 ` [Bug middle-end/97392] " rguenth at gcc dot gnu.org 2020-10-13 8:11 ` marxin at gcc dot gnu.org 2020-10-13 8:45 ` cvs-commit at gcc dot gnu.org 2020-10-13 8:45 ` marxin at gcc dot gnu.org 2020-10-13 14:55 ` msebor at gcc dot gnu.org 2020-11-05 10:30 ` cvs-commit at gcc dot gnu.org 2020-11-05 10:30 ` cvs-commit at gcc dot gnu.org [this message]
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-97392-4-klXf4Rea2O@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).