public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "izbyshev at ispras dot ru" <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:40:27 +0000	[thread overview]
Message-ID: <bug-99903-4-0xq4gndzFq@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

--- Comment #2 from Alexey Izbyshev <izbyshev at ispras dot ru> ---
> Is there a way to bind GCC to a specific core and test again?

Yes, `repro.py` can be run via `start /affinity MASK`. I've started two
experiments, with one- and two-processor masks. They haven't crashed after
several minutes, but I'll wait longer and then report the result.

Anyway, it seems that crashing in `gcc_unreachable()` due to NULL
`context->printer` is still kind-of-a-bug, since it makes it difficult to
understand what went wrong in the first place.

  parent reply	other threads:[~2021-04-04  7:40 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 ` [Bug other/99903] " pinskia at gcc dot gnu.org
2021-04-04  7:40 ` izbyshev at ispras dot ru [this message]
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-0xq4gndzFq@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).