public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/102527] [12 regression] out of memory compiling insn-emit.c
Date: Wed, 29 Sep 2021 21:04:41 +0000 [thread overview]
Message-ID: <bug-102527-4-NnMLlcatC7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102527-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102527
--- Comment #7 from Rainer Orth <ro at gcc dot gnu.org> ---
(In reply to Aldy Hernandez from comment #4)
> Can it be reproduced on a cross? If so, could you post the .ii file with
> your include file peculiarities?
I haven't tried, but expect it should work, provided you run on a 32-bit host
and perhaps limit VM consumption. I expect that depending on the host OSes
VM layout cc1plus may be able to use more of the 4 GB address space on one OS
than the other.
That said, there's a weird problem:
If I run a regular build, I get the `out of memory' error reported. Just
adding
-save-temps to the command line produces a couple of weird warnings/errors:
/var/gcc/reghunt/master/gcc/config/i386/i386.md: In function ‘rtx_insn*
gen_split_495(rtx_insn*, rtx_def**)’:
/var/gcc/reghunt/master/gcc/config/i386/i386.md:20130:29: error: this statement
may fall through [-Werror=implicit-fallthrough=]
20130 | code = swap_condition (code);
| ~~~~~~~~~~~~~~~^~~~~~
/var/gcc/reghunt/master/gcc/config/i386/i386.md:20133:5: note: here
20133 | case GE: case GEU:
| ^~~~
/var/gcc/reghunt/master/gcc/config/i386/i386.md: In function ‘rtx_insn*
gen_split_496(rtx_insn*, rtx_def**)’:
/var/gcc/reghunt/master/gcc/config/i386/i386.md:20130:29: error: this statement
may fall through [-Werror=implicit-fallthrough=]
20130 | code = swap_condition (code);
| ~~~~~~~~~~~~~~~^~~~~~
/var/gcc/reghunt/master/gcc/config/i386/i386.md:20133:5: note: here
20133 | case GE: case GEU:
| ^~~~
/var/gcc/reghunt/master/gcc/config/i386/i386.md: In function ‘rtx_insn*
gen_split_497(rtx_insn*, rtx_def**)’:
/var/gcc/reghunt/master/gcc/config/i386/i386.md:20130:29: error: this statement
may fall through [-Werror=implicit-fallthrough=]
20130 | code = swap_condition (code);
| ~~~~~~~~~~~~~~~^~~~~~
/var/gcc/reghunt/master/gcc/config/i386/i386.md:20133:5: note: here
20133 | case GE: case GEU:
| ^~~~
/var/gcc/reghunt/master/gcc/config/i386/i386.md: In function ‘rtx_insn*
gen_split_498(rtx_insn*, rtx_def**)’:
/var/gcc/reghunt/master/gcc/config/i386/i386.md:20130:29: error: this statement
may fall through [-Werror=implicit-fallthrough=]
20130 | code = swap_condition (code);
| ~~~~~~~~~~~~~~~^~~~~~
/var/gcc/reghunt/master/gcc/config/i386/i386.md:20133:5: note: here
20133 | case GE: case GEU:
| ^~~~
/var/gcc/reghunt/master/gcc/config/i386/i386.md: In function ‘rtx_insn*
gen_split_499(rtx_insn*, rtx_def**)’:
/var/gcc/reghunt/master/gcc/config/i386/i386.md:20130:29: error: this statement
may fall through [-Werror=implicit-fallthrough=]
20130 | code = swap_condition (code);
| ~~~~~~~~~~~~~~~^~~~~~
/var/gcc/reghunt/master/gcc/config/i386/i386.md:20133:5: note: here
20133 | case GE: case GEU:
| ^~~~
/var/gcc/reghunt/master/gcc/config/i386/i386.md: In function ‘rtx_insn*
gen_split_500(rtx_insn*, rtx_def**)’:
/var/gcc/reghunt/master/gcc/config/i386/i386.md:20130:29: error: this statement
may fall through [-Werror=implicit-fallthrough=]
20130 | code = swap_condition (code);
| ~~~~~~~~~~~~~~~^~~~~~
/var/gcc/reghunt/master/gcc/config/i386/i386.md:20133:5: note: here
20133 | case GE: case GEU:
| ^~~~
/var/gcc/reghunt/master/gcc/config/i386/i386.md: In function ‘rtx_insn*
gen_split_501(rtx_insn*, rtx_def**)’:
/var/gcc/reghunt/master/gcc/config/i386/i386.md:20130:29: error: this statement
may fall through [-Werror=implicit-fallthrough=]
20130 | code = swap_condition (code);
| ~~~~~~~~~~~~~~~^~~~~~
/var/gcc/reghunt/master/gcc/config/i386/i386.md:20133:5: note: here
20133 | case GE: case GEU:
| ^~~~
/var/gcc/reghunt/master/gcc/config/i386/i386.md: In function ‘rtx_insn*
gen_split_502(rtx_insn*, rtx_def**)’:
/var/gcc/reghunt/master/gcc/config/i386/i386.md:20130:29: error: this statement
may fall through [-Werror=implicit-fallthrough=]
20130 | code = swap_condition (code);
| ~~~~~~~~~~~~~~~^~~~~~
/var/gcc/reghunt/master/gcc/config/i386/i386.md:20133:5: note: here
20133 | case GE: case GEU:
| ^~~~
/var/gcc/reghunt/master/gcc/config/i386/sse.md: In function ‘rtx_insn*
gen_split_2186(rtx_insn*, rtx_def**)’:
/var/gcc/reghunt/master/gcc/config/i386/sse.md:18256:19: error: this statement
may fall through [-Werror=implicit-fallthrough=]
18256 | operands[1] = tmp;
| ~~~~~~~~~~~~^~~~~
/var/gcc/reghunt/master/gcc/config/i386/sse.md:18258:5: note: here
18258 | case 32:
| ^~~~
/var/gcc/reghunt/master/gcc/config/i386/sse.md: In function ‘rtx_insn*
gen_split_2187(rtx_insn*, rtx_def**)’:
/var/gcc/reghunt/master/gcc/config/i386/sse.md:18256:19: error: this statement
may fall through [-Werror=implicit-fallthrough=]
18256 | operands[1] = tmp;
| ~~~~~~~~~~~~^~~~~
/var/gcc/reghunt/master/gcc/config/i386/sse.md:18258:5: note: here
18258 | case 32:
| ^~~~
and (if adding -Wno-error to avoid that) while cc1plus still consumes in excess
of 3 GB VM space, the compilation finally succeeds.
I'm attaching the preprocessed output nonetheless; maybe it's still helpful.
next prev parent reply other threads:[~2021-09-29 21:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 13:45 [Bug bootstrap/102527] New: " ro at gcc dot gnu.org
2021-09-29 13:46 ` [Bug bootstrap/102527] " ro at gcc dot gnu.org
2021-09-29 14:28 ` dje at gcc dot gnu.org
2021-09-29 14:31 ` aldyh at gcc dot gnu.org
2021-09-29 14:33 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-09-29 15:06 ` aldyh at gcc dot gnu.org
2021-09-29 15:18 ` aldyh at gcc dot gnu.org
2021-09-29 15:22 ` aldyh at gcc dot gnu.org
2021-09-29 21:04 ` ro at gcc dot gnu.org [this message]
2021-09-29 21:05 ` ro at gcc dot gnu.org
2021-09-29 22:15 ` ro at gcc dot gnu.org
2021-09-29 22:16 ` ro at gcc dot gnu.org
2021-09-30 0:19 ` aldyh at redhat dot com
2021-09-30 6:22 ` aldyh at gcc dot gnu.org
2021-09-30 10:29 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-09-30 10:46 ` aldyh 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-102527-4-NnMLlcatC7@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).