public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/99903] 32-bit x86 frontends randomly crash while reporting timing on Windows Date: Sun, 04 Apr 2021 07:13:19 +0000 [thread overview] Message-ID: <bug-99903-4-DEhmDIJt3L@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99903-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99903 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Build|i686-w64-mingw32 | Status|UNCONFIRMED |WAITING Target|i686-w64-mingw32 | Ever confirmed|0 |1 Last reconfirmed| |2021-04-04 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- I don't see anything wrong with the code. clock () is being used here. Maybe there is a bug in the implementation of clock where it is not always incrementing. Since it is random, maybe the problem is switching between the cores. Is there a way to bind GCC to a specific core and test again?
next prev parent reply other threads:[~2021-04-04 7:13 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-04 6:54 [Bug other/99903] New: " izbyshev at ispras dot ru 2021-04-04 7:13 ` pinskia at gcc dot gnu.org [this message] 2021-04-04 7:40 ` [Bug other/99903] " izbyshev at ispras dot ru 2021-04-06 15:48 ` izbyshev at ispras dot ru 2021-05-04 15:14 ` amonakov 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-99903-4-DEhmDIJt3L@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).