From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4E6083858C5E; Wed, 8 Nov 2023 19:00:48 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4E6083858C5E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1699470048; bh=X75uhDD0d3SvkxW2g2dJ1Qb0iOiyQa9fj50+tyRYC/4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=BHy0KvAqICkLnbZ9MfAPt7YAHiAeMFvdK4PZEVITwQzLXFNfcyoc3xSr/pbgJ0Y7s 8gHPqwTj2nk+dMix3NlvO0VaFD6rnGrI+V9hK28Q4cKrBIGRAVu/Vyzj6ge87GmvA9 zabbsRTJLCAMvt4EUnxJvcAiuGP0iRtfcBw46u0I= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/8670] Alignment problem in std::basic_string Date: Wed, 08 Nov 2023 19:00:47 +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: 3.1 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: 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=3D8670 --- Comment #24 from Jonathan Wakely --- Oh, but this would be an ABI break. When using the explicit instantiation definitions in libstdc++.so allocations and deallocations will match because both will come from the library. But if anything is inlined, code compiled against older gcc headers might allocate N bytes from _Raw_bytes_alloc, and other code might deallocate N2 bytes from _Rep_alloc, where N !=3D N2.=