From: John David Anglin <dave.anglin@bell.net>
To: Arnd Bergmann <arnd@arndb.de>,
Abd-Alrhman Masalkhi <abd.masalkhi@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Jens Axboe <axboe@kernel.dk>,
bernie@develer.com, Parisc List <linux-parisc@vger.kernel.org>,
linux-block <linux-block@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: div_u64/do_div stack size usage, was Re: [v3] block: Removed a warning while compiling with a cross compiler for parisc
Date: Wed, 7 Jul 2021 10:36:38 -0400 [thread overview]
Message-ID: <f9293c4d-bb4e-bcf0-183e-90cf5192a725@bell.net> (raw)
In-Reply-To: <CAK8P3a23=tcWx8iWNAKXcT9TRgPrZbEVVy9a_ad29hSde_jkKg@mail.gmail.com>
On 2021-07-07 4:17 a.m., Arnd Bergmann wrote:
> I have also tried it with the other gcc versions and shown that it
> happens with every older compiler as well, but it does not happen
> with gcc-10 or gcc-11, which bring the frame size down to 164 or
> 172 bytes respectively. gcc-10 also fixes similar warnings for
> net/ipv4/tcp_input.c, net/sunrpc/stats.c and lib/xxhash.c that
> fly under the radar with the default warning level.
>
> My first thought was this was a result of -finline-functions getting
> enabled by default in gcc-10, but enabling it on gcc-9 did not
> help here. It's likely that the gcc behavior was fixed in the process
> of enabling the more aggressive inliner by default though.
A number of improvements were made to the calculation of RTX costs in gcc-10 and gcc-11.
These dramatically affect inlining and the compilation time for xxhash.c on parisc. The problem
is pretty much fixed for the 32-bit target but more work is needed for the 64-bit target.
See:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87256
Dave
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2021-07-07 14:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 11:19 [PATCH v3] block: Removed a warning while compiling with a cross compiler for parisc Abd-Alrhman Masalkhi
2021-07-06 13:59 ` Christoph Hellwig
2021-07-06 15:30 ` [v3] " Abd-Alrhman Masalkhi
2021-07-06 17:01 ` div_u64/do_div stack size usage, was " Christoph Hellwig
2021-07-06 17:35 ` Arnd Bergmann
2021-07-06 20:59 ` Abd-Alrhman Masalkhi
2021-07-07 8:17 ` Arnd Bergmann
2021-07-07 13:36 ` Helge Deller
2021-07-07 20:39 ` Arnd Bergmann
2021-07-08 9:29 ` Helge Deller
2021-07-08 11:37 ` Arnd Bergmann
2021-07-08 15:01 ` John David Anglin
2021-07-07 14:36 ` John David Anglin [this message]
2021-07-07 15:30 ` Abd-Alrhman Masalkhi
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=f9293c4d-bb4e-bcf0-183e-90cf5192a725@bell.net \
--to=dave.anglin@bell.net \
--cc=abd.masalkhi@gmail.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=bernie@develer.com \
--cc=dan.carpenter@oracle.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.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 NNTP newsgroup(s).