public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/97314] bootstrap failure on i686-linux-gnu with --enable-checking=yes,extra,rtl
Date: Tue, 17 Nov 2020 15:14:49 +0000	[thread overview]
Message-ID: <bug-97314-4-OPD5Zzn7Mw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97314-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97314

rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rsandifo at gcc dot gnu.org

--- Comment #3 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
I see the same thing for arm-linux-gnueabihf on trunk, also on
insn-extract.o.  It's specific to RTL checking for me too.

I found it does work if I bootstrap with --enable-checking=yes,extra,
flip ENABLE_RTL_CHECKING to 1 in auto-host.h, and then recompile
insn-extract.c.  But it does take a large amount of VM:

phase parsing                      :  51.10 ( 27%)  43.64 ( 74%)  94.74 ( 38%) 
1334M ( 73%)

This used to work “a while ago” but I don't know when it stopped.

The file has 9975 lines, 435KiB, but that's a bairn compared to some
of the stuff we kick out.  Perhaps it's just the sheer number of
(nested) XEXP macro expansions?

  parent reply	other threads:[~2020-11-17 15:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07  8:06 [Bug bootstrap/97314] New: " doko at debian dot org
2020-10-07  8:46 ` [Bug bootstrap/97314] " rguenth at gcc dot gnu.org
2020-10-07  9:00 ` jakub at gcc dot gnu.org
2020-11-17 15:14 ` rsandifo at gcc dot gnu.org [this message]
2020-12-07  8:35 ` doko at debian dot 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-97314-4-OPD5Zzn7Mw@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).