public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/98863] [11 Regression] WRF with LTO consumes a lot of memory in REE, FWPROP and x86 specific passes
Date: Mon, 08 Feb 2021 12:44:01 +0000 [thread overview]
Message-ID: <bug-98863-4-2kEv6B8Xq2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98863-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98863
--- Comment #43 from Richard Biener <rguenth at gcc dot gnu.org> ---
So module_configure.fppized.f90 is one of the interesting ones (IIRC lot of
small init loops), module_first_rk_step_part1.fppized.f90 is the one with most
obvious DF and fwprop participation, that one also has complete unrolling.
/home/rguenther/install/gcc-11.0/usr/local/bin/gfortran -c -o
start_em.fppized.o -I. -I./netcdf/include -I./inc -Ofast -march=znver2
-ftime-report -std=legacy -fconvert=big-endian -fno-openmp -g0
start_em.fppized.f90
df reaching defs : 0.96 ( 3%) 0.02 ( 3%) 0.94 ( 3%)
0 ( 0%)
df live regs : 1.15 ( 4%) 0.00 ( 0%) 1.13 ( 4%)
0 ( 0%)
df live&initialized regs : 1.08 ( 4%) 0.01 ( 2%) 1.18 ( 4%)
0 ( 0%)
tree forward propagate : 0.09 ( 0%) 0.01 ( 2%) 0.08 ( 0%)
2217k ( 0%)
complete unrolling : 1.00 ( 3%) 0.02 ( 3%) 1.01 ( 3%)
56M ( 12%)
forward prop : 0.93 ( 3%) 0.18 ( 29%) 1.10 ( 4%)
388k ( 0%)
TOTAL : 30.60 0.62 31.23
492M
/home/rguenther/install/gcc-11.0/usr/local/bin/gfortran -c -o
module_advect_em.fppized.o -I. -I./netcdf/include -I./inc -Ofast -march=znver2
-ftime-report -std=legacy -fconvert=big-endian -fno-openmp -g0
module_advect_em.fppized.f90
df reaching defs : 0.28 ( 1%) 0.00 ( 0%) 0.30 ( 1%)
0 ( 0%)
df live regs : 1.45 ( 5%) 0.00 ( 0%) 1.35 ( 4%)
0 ( 0%)
df live&initialized regs : 0.54 ( 2%) 0.00 ( 0%) 0.64 ( 2%)
0 ( 0%)
tree forward propagate : 0.08 ( 0%) 0.00 ( 0%) 0.13 ( 0%)
2824k ( 0%)
complete unrolling : 0.99 ( 3%) 0.03 ( 9%) 1.05 ( 3%)
78M ( 8%)
forward prop : 0.24 ( 1%) 0.00 ( 0%) 0.20 ( 1%)
1270k ( 0%)
TOTAL : 31.59 0.34 31.96
974M
/home/rguenther/install/gcc-11.0/usr/local/bin/gfortran -c -o
module_first_rk_step_part1.fppized.o -I. -I./netcdf/include -I./inc -Ofast
-march=znver2 -ftime-report -std=legacy -fconvert=big-endian -fno-openmp -g0
module_first_rk_step_part1.fppized.f90
df reaching defs : 2.69 ( 4%) 0.04 ( 3%) 2.81 ( 5%)
0 ( 0%)
df live regs : 1.76 ( 3%) 0.01 ( 1%) 1.71 ( 3%)
0 ( 0%)
df live&initialized regs : 1.57 ( 3%) 0.01 ( 1%) 1.58 ( 3%)
0 ( 0%)
tree forward propagate : 0.20 ( 0%) 0.02 ( 2%) 0.19 ( 0%)
4095k ( 0%)
complete unrolling : 3.25 ( 5%) 0.04 ( 3%) 3.27 ( 5%)
94M ( 11%)
forward prop : 2.79 ( 5%) 0.38 ( 30%) 3.16 ( 5%)
765k ( 0%)
TOTAL : 60.41 1.27 61.72
873M
/home/rguenther/install/gcc-11.0/usr/local/bin/gfortran -c -o
solve_em.fppized.o -I. -I./netcdf/include -I./inc -Ofast -march=znver2
-ftime-report -std=legacy -fconvert=big-endian -fno-openmp -g0
solve_em.fppized.f90
df reaching defs : 1.57 ( 5%) 0.01 ( 2%) 1.50 ( 5%)
0 ( 0%)
df live regs : 2.22 ( 7%) 0.01 ( 2%) 2.24 ( 7%)
0 ( 0%)
df live&initialized regs : 2.83 ( 9%) 0.01 ( 2%) 2.81 ( 9%)
0 ( 0%)
tree forward propagate : 0.15 ( 0%) 0.00 ( 0%) 0.15 ( 0%)
2644k ( 0%)
complete unrolling : 1.11 ( 4%) 0.02 ( 4%) 1.12 ( 4%)
86M ( 14%)
forward prop : 0.75 ( 2%) 0.08 ( 14%) 0.84 ( 3%)
495k ( 0%)
TOTAL : 31.21 0.57 31.80
629M
In the end LTO makes the case unique still ...
And then there's of course one other frequently reported bug:
/home/rguenther/install/gcc-11.0/usr/local/bin/gfortran -c -o
module_alloc_space_2.fppized.o -I. -I./netcdf/include -I./inc -Ofast
-march=znver2 -ftime-report -std=legacy -fconvert=big-endian -fno-openmp -g0
module_alloc_space_2.fppized.f90
load CSE after reload : 10.18 ( 37%) 0.00 ( 0%) 10.19 ( 37%)
14k ( 0%)
TOTAL : 27.28 0.33 27.63
333M
next prev parent reply other threads:[~2021-02-08 12:44 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 11:19 [Bug rtl-optimization/98863] New: WRF with LTO consumes a lot of memory in split2 pass marxin at gcc dot gnu.org
2021-01-28 11:20 ` [Bug rtl-optimization/98863] " marxin at gcc dot gnu.org
2021-01-28 13:18 ` rguenth at gcc dot gnu.org
2021-01-28 13:21 ` marxin at gcc dot gnu.org
2021-01-28 14:14 ` marxin at gcc dot gnu.org
2021-01-28 14:20 ` rguenth at gcc dot gnu.org
2021-01-28 14:24 ` rguenth at gcc dot gnu.org
2021-01-28 15:09 ` marxin at gcc dot gnu.org
2021-01-28 15:15 ` rguenth at gcc dot gnu.org
2021-01-28 15:17 ` rguenth at gcc dot gnu.org
2021-01-28 15:18 ` rguenth at gcc dot gnu.org
2021-01-28 15:30 ` rguenth at gcc dot gnu.org
2021-01-29 8:47 ` rguenth at gcc dot gnu.org
2021-01-29 9:03 ` rguenth at gcc dot gnu.org
2021-01-29 9:47 ` rguenth at gcc dot gnu.org
2021-01-29 9:56 ` marxin at gcc dot gnu.org
2021-01-29 10:18 ` marxin at gcc dot gnu.org
2021-01-29 10:24 ` rguenther at suse dot de
2021-01-29 11:03 ` rguenth at gcc dot gnu.org
2021-01-29 11:03 ` [Bug rtl-optimization/98863] WRF with LTO consumes a lot of memory in REE pass rguenth at gcc dot gnu.org
2021-01-29 11:38 ` marxin at gcc dot gnu.org
2021-01-29 12:13 ` rguenth at gcc dot gnu.org
2021-01-29 12:50 ` [Bug rtl-optimization/98863] WRF with LTO consumes a lot of memory in REE, CPROP, PRE and LRA passes rguenth at gcc dot gnu.org
2021-01-29 12:57 ` marxin at gcc dot gnu.org
2021-01-29 13:01 ` cvs-commit at gcc dot gnu.org
2021-01-29 13:23 ` rguenth at gcc dot gnu.org
2021-01-29 13:37 ` marxin at gcc dot gnu.org
2021-01-29 14:39 ` rguenth at gcc dot gnu.org
2021-01-29 15:01 ` rguenth at gcc dot gnu.org
2021-01-29 15:56 ` hjl.tools at gmail dot com
2021-01-29 16:32 ` cvs-commit at gcc dot gnu.org
2021-02-01 8:22 ` cvs-commit at gcc dot gnu.org
2021-02-01 9:31 ` marxin at gcc dot gnu.org
2021-02-01 10:41 ` rguenth at gcc dot gnu.org
2021-02-01 12:07 ` [Bug rtl-optimization/98863] WRF with LTO consumes a lot of memory in REE, FWPROP and x86 specific passes rguenth at gcc dot gnu.org
2021-02-01 12:30 ` rsandifo at gcc dot gnu.org
2021-02-01 12:32 ` rguenth at gcc dot gnu.org
2021-02-01 12:45 ` [Bug rtl-optimization/98863] [11 Regression] " rguenth at gcc dot gnu.org
2021-02-01 13:35 ` cvs-commit at gcc dot gnu.org
2021-02-03 10:27 ` cvs-commit at gcc dot gnu.org
2021-02-03 12:33 ` cvs-commit at gcc dot gnu.org
2021-02-08 8:45 ` rsandifo at gcc dot gnu.org
2021-02-08 9:01 ` rguenther at suse dot de
2021-02-08 9:23 ` richard.sandiford at arm dot com
2021-02-08 9:46 ` rguenth at gcc dot gnu.org
2021-02-08 12:44 ` rguenth at gcc dot gnu.org [this message]
2021-02-09 12:07 ` cvs-commit at gcc dot gnu.org
2021-02-09 12:40 ` rguenth at gcc dot gnu.org
2021-02-10 13:51 ` rguenth at gcc dot gnu.org
2021-02-15 15:06 ` cvs-commit at gcc dot gnu.org
2021-02-15 15:34 ` rsandifo 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-98863-4-2kEv6B8Xq2@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).