public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/51041] register allocation of SSE register in loop with across eh edges
Date: Fri, 07 Jul 2023 15:13:24 +0000	[thread overview]
Message-ID: <bug-51041-4-a16DlQAMij@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51041-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
I believe it is the same problem as PR110215 which was solved recently by
checking whether pseudo values are used in the exception handler and the
handler does not return control flow back to the function code.

So I guess this problem was solved too.

      parent reply	other threads:[~2023-07-07 15:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08 22:21 [Bug other/51041] New: g++ strange optimisation behaviour fb.programming at gmail dot com
2011-11-08 22:23 ` [Bug other/51041] " fb.programming at gmail dot com
2011-11-08 22:31 ` [Bug rtl-optimization/51041] " pinskia at gcc dot gnu.org
2023-07-07 15:13 ` vmakarov at gcc dot gnu.org [this message]

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-51041-4-a16DlQAMij@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).