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 tree-optimization/107868] [10 regression] Wrong code on AArch64 at -O1 with new/delete
Date: Mon, 28 Nov 2022 18:40:08 +0000	[thread overview]
Message-ID: <bug-107868-4-S3WlJ7cOJM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107868-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |NEW
           Assignee|rguenth at gcc dot gnu.org         |unassigned at gcc dot gnu.org

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
It also depends on r11-3386-g9e64f17d044767 for a testsuite adjustment and
also r11-3612-g4f4ced28826ece to further fix the C++ frontend side and
avoid regressing g++.dg/pr94314.C but that doesn't apply cleanly.

So there's definitely too much to backport for this last GCC 10 release.  At
least I'm now going to stop chasing all related commits ...

  parent reply	other threads:[~2022-11-28 18:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25 10:33 [Bug tree-optimization/107868] New: " victor.donascimento at arm dot com
2022-11-25 12:23 ` [Bug tree-optimization/107868] " marxin at gcc dot gnu.org
2022-11-25 12:26 ` rguenth at gcc dot gnu.org
2022-11-28 16:13 ` rguenth at gcc dot gnu.org
2022-11-28 16:29 ` rguenth at gcc dot gnu.org
2022-11-28 17:59 ` victor.donascimento at arm dot com
2022-11-28 18:40 ` rguenth at gcc dot gnu.org [this message]
2023-07-07 10:05 ` rguenth 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-107868-4-S3WlJ7cOJM@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).