From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 6588A386F81A; Sun, 29 Nov 2020 15:35:50 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6588A386F81A
From: "src at andyf dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/98052] New: Allocation with new and deallocation with
 std::allocator should result in an error
Date: Sun, 29 Nov 2020 15:35:50 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.2.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: src at andyf dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-98052-4@http.gcc.gnu.org/bugzilla/>
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
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Nov 2020 15:35:50 -0000

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

            Bug ID: 98052
           Summary: Allocation with new and deallocation with
                    std::allocator should result in an error
           Product: gcc
           Version: 10.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: src at andyf dot de
  Target Milestone: ---

Hello,

the following code compiles without an error (https://godbolt.org/z/oPG8Ea)=
 in
GCC:


#include <memory>

constexpr auto fun()
{
    int* i =3D new int{4};

    std::allocator<int> a{};
    a.deallocate(i, 1);

    return 0;
}

int main()
{
    constexpr auto f =3D fun();
}


In the constexpr function fun, an int is allocated with new and free'd with
std::allocator's deallocate. According to N4868 [allocator.members] p6, a
precondition for deallocate is that the memory was previously allocated with
allocate. Clang does reject the code with:

note: 'std::allocator<...>::deallocate' used to delete pointer to object
allocated with 'new'

The behavior of Clang seems to be consistent with the wording. GCC incorrec=
tly
allows this code to compile.


Best,

   Andreas=