From: Gerald Pfeifer <gerald@pfeifer.com>
To: Aldy Hernandez <aldyh@redhat.com>, Jeff Law <jeffreyalaw@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Replace VRP threader with a hybrid forward threader.
Date: Fri, 1 Oct 2021 12:55:56 +0200 (CEST) [thread overview]
Message-ID: <6dccbae9-eab1-d1bc-551e-97188483e18@pfeifer.com> (raw)
In-Reply-To: <20210924154653.1108992-1-aldyh@redhat.com>
On Fri, 24 Sep 2021, Aldy Hernandez via Gcc-patches wrote:
> This patch implements the new hybrid forward threader and replaces the
> embedded VRP threader with it.
I'm not sure this is the right of the patches to follow-up around this,
but between Jeff writing
"Note we've got massive failures in the tester starting sometime
yesterday and I suspect all the threader work. So I'm going to slow
down on reviews of that code as we stabilize stuff."
in another thread and you
"There seems to be a memory consumption issue on 32 bit hosts after
the hybrid threader patchset. I'm having a hard time reproducing..."
in yet another I can report that my i586-unknown-freebsd11 nightly tester
started to fail on Sep 28 at 00:40 UTC, still failed Sep 29 and Sep 30,
and successfully passed last night.
Failures were all at the same point in all-stage2-gcc:
cc1plus: out of memory allocating 65536 bytes after a total of 0 bytes
gmake[3]: *** [Makefile:1136: insn-emit.o] Error 1
cc1plus: out of memory allocating 65536 bytes after a total of 0 bytes
gmake[3]: *** [Makefile:1136: insn-emit.o] Error 1
cc1plus: out of memory allocating 86776 bytes after a total of 0 bytes
gmake[3]: *** [Makefile:1136: insn-emit.o] Error 1
Is this under control now, or was last night just a lucky one?
Since that reproduced somewhat regularly, how may I be able to help?
Gerald
next prev parent reply other threads:[~2021-10-01 10:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 15:46 Aldy Hernandez
2021-09-25 19:25 ` Bernhard Reutner-Fischer
[not found] ` <C9A89E9C-89D4-45A9-8DFC-BA0536D24611@gmail.com>
[not found] ` <CAGm3qMVTw4hEvqNJmSaXbuUArYjMUoX7o-YOgMi2bLAm1i12-Q@mail.gmail.com>
2021-09-29 9:20 ` Bernhard Reutner-Fischer
2021-09-29 15:45 ` Jeff Law
2021-09-27 15:01 ` Jeff Law
2021-09-27 15:27 ` Aldy Hernandez
2021-09-27 16:07 ` Aldy Hernandez
2021-09-27 17:28 ` Richard Biener
2021-10-14 12:29 ` Aldy Hernandez
2021-10-14 12:47 ` Richard Biener
2021-10-01 10:55 ` Gerald Pfeifer [this message]
2021-10-01 11:03 ` Aldy Hernandez
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=6dccbae9-eab1-d1bc-551e-97188483e18@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
/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).