public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <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, 04 Mar 2021 12:00:28 +0000 [thread overview]
Message-ID: <bug-97090-4-Xs18XdPNFR@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
--- Comment #12 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #11 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
> Re comment #10: I just tested unknown-fns-4.c and malloc-vs-local-1b.c 500
> times each on a --target=i386-pc-solaris2.11 build using the script from
> comment #8 and the results were identical each time. So hopefully the
> nondeterminism is fixed, at least.
Indeed: the last time I saw the flakyness in my daily builds was on 20210106.
next prev parent reply other threads:[~2021-03-04 12:00 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
2021-03-03 23:24 ` dmalcolm at gcc dot gnu.org
2021-03-04 12:00 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
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-Xs18XdPNFR@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: link
Be 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).