public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "torvalds@linux-foundation.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105930] [12/13 Regression] Excessive stack spill generation on 32-bit x86
Date: Mon, 13 Jun 2022 18:31:22 +0000	[thread overview]
Message-ID: <bug-105930-4-XEPt1ZEXzl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105930-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from Linus Torvalds <torvalds@linux-foundation.org> ---
(In reply to Samuel Neves from comment #13)
> Something simple like this -- https://godbolt.org/z/61orYdjK7 -- already
> exhibits the effect. 

Yup.

That's a much better test-case. I think you should attach it to the gcc
bugzilla, I don't know how long godbolt remembers those links.

But godbolt here is good for another thing: select clang-14 as the compiler,
and you realize how even gcc-11 is actually doing a really really bad job.

And I'm not saying that to shame anybody: I think it's more a sign that maybe
the issue is actually much deeper, and that the problem already exists in
gcc-11, but some small perturbation then just makes an already existing problem
much worse in gcc-12.

So that commit I bisected to is probably almost entirely unrelated, and it is
just the thing that turns up the bad behavior to 11.

  parent reply	other threads:[~2022-06-13 18:31 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11 20:51 [Bug c/105930] New: " torvalds@linux-foundation.org
2022-06-11 23:20 ` [Bug target/105930] " torvalds@linux-foundation.org
2022-06-11 23:54 ` [Bug target/105930] [12/13 Regression] " pinskia at gcc dot gnu.org
2022-06-11 23:59 ` pinskia at gcc dot gnu.org
2022-06-12  0:20 ` torvalds@linux-foundation.org
2022-06-12  0:20 ` torvalds@linux-foundation.org
2022-06-12  0:27 ` torvalds@linux-foundation.org
2022-06-12  2:26 ` sneves at dei dot uc.pt
2022-06-12  6:28 ` roger at nextmovesoftware dot com
2022-06-12 16:18 ` torvalds@linux-foundation.org
2022-06-12 16:35 ` torvalds@linux-foundation.org
2022-06-12 17:30 ` torvalds@linux-foundation.org
2022-06-13  9:29 ` jakub at gcc dot gnu.org
2022-06-13 17:39 ` torvalds@linux-foundation.org
2022-06-13 18:23 ` sneves at dei dot uc.pt
2022-06-13 18:31 ` torvalds@linux-foundation.org [this message]
2022-06-14  7:57 ` rguenth at gcc dot gnu.org
2022-06-14  8:50 ` jakub at gcc dot gnu.org
2022-06-14  9:42 ` jakub at gcc dot gnu.org
2022-06-14  9:50 ` jakub at gcc dot gnu.org
2022-06-16 10:06 ` arnd at linaro dot org
2022-06-24  6:17 ` cvs-commit at gcc dot gnu.org
2022-06-24 16:45 ` torvalds@linux-foundation.org
2022-06-24 16:55 ` jakub at gcc dot gnu.org
2022-06-24 17:06 ` torvalds@linux-foundation.org
2022-06-24 17:19 ` torvalds@linux-foundation.org
2022-06-24 17:33 ` jakub at gcc dot gnu.org
2022-06-30 10:03 ` cvs-commit at gcc dot gnu.org
2022-07-10  8:01 ` roger at nextmovesoftware dot com
2022-07-10 16:41 ` torvalds@linux-foundation.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-105930-4-XEPt1ZEXzl@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).