public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/97090] gcc.dg/analyzer/malloc-vs-local-1b.c fails on arm and powerpc64*-linux-gnu Date: Thu, 10 Dec 2020 13:48:22 +0000 [thread overview] Message-ID: <bug-97090-4-ot17tKNbtS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97090-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97090 Rainer Orth <ro at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |11.0 CC| |ro at gcc dot gnu.org --- Comment #10 from Rainer Orth <ro at gcc dot gnu.org> --- I see the same flakyness of both gcc.dg/analyzer/unknown-fns-4.c (usually XPASSing XPASS: gcc.dg/analyzer/unknown-fns-4.c (test for warnings, line 13) but PASSing once in a while) and gcc.dg/analyzer/malloc-vs-local-1b.c (usually FAILing FAIL: gcc.dg/analyzer/malloc-vs-local-1b.c (test for bogus messages, line 170) but PASSing once in a while) on both sparc-sun-solaris2.11 and i386-pc-solaris2.11.
next prev parent reply other threads:[~2020-12-10 13:48 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-17 16:14 [Bug analyzer/97090] New: gcc.dg/analyzer/malloc-vs-local-1b.c fails on arm clyon at gcc dot gnu.org 2020-09-18 8:57 ` [Bug analyzer/97090] " clyon at gcc dot gnu.org 2020-09-18 9:09 ` clyon at gcc dot gnu.org 2020-09-18 9:12 ` jakub at gcc dot gnu.org 2020-10-28 19:57 ` [Bug analyzer/97090] gcc.dg/analyzer/malloc-vs-local-1b.c fails on arm and powerpc64*-linux-gnu dmalcolm at gcc dot gnu.org 2020-10-28 19:59 ` dmalcolm at gcc dot gnu.org 2020-10-28 20:02 ` dmalcolm at gcc dot gnu.org 2020-10-28 20:04 ` dmalcolm at gcc dot gnu.org 2020-10-29 0:42 ` dmalcolm at gcc dot gnu.org 2020-11-30 21:12 ` seurer at gcc dot gnu.org 2020-12-10 13:48 ` ro at gcc dot gnu.org [this message] 2021-03-03 23:24 ` dmalcolm at gcc dot gnu.org 2021-03-04 12:00 ` ro at CeBiTec dot Uni-Bielefeld.DE 2021-04-27 11:39 ` jakub at gcc dot gnu.org 2021-07-28 7:04 ` rguenth at gcc dot gnu.org 2021-11-30 23:18 ` dmalcolm at gcc dot gnu.org 2021-12-01 8:51 ` clyon at gcc dot gnu.org 2021-12-02 10:50 ` ro at CeBiTec dot Uni-Bielefeld.DE 2021-12-02 14:06 ` 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-97090-4-ot17tKNbtS@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).