From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4C0CC38582A2; Tue, 9 Jan 2024 22:33:45 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4C0CC38582A2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1704839625; bh=ocwrtZEPTtbSayF0V80fQ+gilZ9TH9KNgbzmvmGtI80=; h=From:To:Subject:Date:In-Reply-To:References:From; b=cjn6qHtDsxQWIuQ8FP4HVXBBGay/yYFUj1Q+WYStq8UKBsAQZY1HDAgUPmu2k5Gzx mw3L+J7YT9y0mrVoK5GHbdUmOeBvdEoA+31Aaz5NLhXeGm1qfSUFXt4srVbh5gXFN8 5M0DIXFN3/6haH2P55+gpsmQHwJGTilUwOUuUf5g= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/113258] Pre-C++17 code that replaces malloc/free crashes when mixed with post-C++17 code that uses the align_val_t variants of new/delete Date: Tue, 09 Jan 2024 22:33:43 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113258 Jonathan Wakely changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu= .org Resolution|INVALID |--- Status|RESOLVED |ASSIGNED --- Comment #23 from Jonathan Wakely --- And what matters is not that it's pre-C++17 code that replaces malloc/free,= but pre-C11. The C++ standard version being used by the malloc-replacing librar= y is irrelevant, what matters is how dated the malloc replacement is. A C11-aware malloc replacement should also replace aligned_alloc. Anyway, patch posted: https://gcc.gnu.org/pipermail/gcc-patches/2024-January/642354.html=