public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107248] wrong scheduling of stack adjustment in leaf function at -O2 Date: Fri, 14 Oct 2022 10:03:37 +0000 [thread overview] Message-ID: <bug-107248-4-5cpaotaoz1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107248-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107248 Eric Botcazou <ebotcazou at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Target Milestone|--- |10.5 Resolution|--- |FIXED --- Comment #9 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- Fixed on all active branches, but the fix should be backportable onto older release branches without any change. Thanks for reporting the problem.
next prev parent reply other threads:[~2022-10-14 10:03 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-13 13:21 [Bug rtl-optimization/107248] New: Sparc V8 Invalid Stack Pointer Code dennis.borde at ohb dot de 2022-10-13 13:25 ` [Bug rtl-optimization/107248] " dennis.borde at ohb dot de 2022-10-13 20:28 ` [Bug target/107248] " pinskia at gcc dot gnu.org 2022-10-13 22:09 ` [Bug target/107248] wrong scheduling of stack adjustment in leaf function at -O2 ebotcazou at gcc dot gnu.org 2022-10-13 22:10 ` ebotcazou at gcc dot gnu.org 2022-10-14 9:56 ` cvs-commit at gcc dot gnu.org 2022-10-14 9:57 ` cvs-commit at gcc dot gnu.org 2022-10-14 9:58 ` cvs-commit at gcc dot gnu.org 2022-10-14 10:00 ` cvs-commit at gcc dot gnu.org 2022-10-14 10:03 ` ebotcazou at gcc dot gnu.org [this message] 2022-10-17 11:05 ` dennis.borde at ohb dot de 2022-10-25 8:00 ` ebotcazou at gcc dot gnu.org 2023-01-03 8:30 ` cederman at gaisler dot com 2023-01-03 8:58 ` ebotcazou 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-107248-4-5cpaotaoz1@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: linkBe 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).