public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113476] [14 Regression] irange::maybe_resize leaks memory via IPA VRP
Date: Wed, 21 Feb 2024 11:25:02 +0000	[thread overview]
Message-ID: <bug-113476-4-CgLwQOvuC5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113476-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Aldy Hernandez from comment #11)
> Both patches pass test.  Up to the release maintainers to decide if they
> want to include them in this release.  Otherwise, I'll queue them up for
> later.

This is an important regression, why shouldn't it be included in GCC 14?
GCC trunk is open for regression and documentation fixes...

  parent reply	other threads:[~2024-02-21 11:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 11:43 [Bug tree-optimization/113476] New: " rguenth at gcc dot gnu.org
2024-01-18 11:43 ` [Bug tree-optimization/113476] " rguenth at gcc dot gnu.org
2024-01-18 11:48 ` rguenth at gcc dot gnu.org
2024-01-18 11:50 ` rguenth at gcc dot gnu.org
2024-01-18 13:32 ` rguenth at gcc dot gnu.org
2024-01-22 17:48 ` jamborm at gcc dot gnu.org
2024-01-23  6:58 ` rguenth at gcc dot gnu.org
2024-02-19 15:05 ` jamborm at gcc dot gnu.org
2024-02-21  9:15 ` aldyh at gcc dot gnu.org
2024-02-21  9:17 ` aldyh at gcc dot gnu.org
2024-02-21  9:18 ` aldyh at gcc dot gnu.org
2024-02-21  9:19 ` aldyh at gcc dot gnu.org
2024-02-21 11:22 ` aldyh at gcc dot gnu.org
2024-02-21 11:25 ` jakub at gcc dot gnu.org [this message]
2024-02-21 11:55 ` aldyh at gcc dot gnu.org
2024-02-21 12:10 ` jakub at gcc dot gnu.org
2024-02-21 14:43 ` [Bug ipa/113476] " cvs-commit at gcc dot gnu.org
2024-02-21 14:44 ` jamborm at gcc dot gnu.org
2024-02-22  7:38 ` rguenther at suse dot de
2024-02-22 16:07 ` aldyh 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-113476-4-CgLwQOvuC5@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).