public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-98052-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            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 = new int{4};

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

    return 0;
}

int main()
{
    constexpr auto f = 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 incorrectly
allows this code to compile.


Best,

   Andreas

             reply	other threads:[~2020-11-29 15:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-29 15:35 src at andyf dot de [this message]
2020-11-29 22:07 ` [Bug c++/98052] " redi at gcc dot gnu.org
2022-11-06 17:24 ` pinskia 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-98052-4@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).