public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/98052] New: Allocation with new and deallocation with std::allocator should result in an error
@ 2020-11-29 15:35 src at andyf dot de
  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
  0 siblings, 2 replies; 3+ messages in thread
From: src at andyf dot de @ 2020-11-29 15:35 UTC (permalink / raw)
  To: gcc-bugs

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug c++/98052] Allocation with new and deallocation with std::allocator should result in an error
  2020-11-29 15:35 [Bug c++/98052] New: Allocation with new and deallocation with std::allocator should result in an error src at andyf dot de
@ 2020-11-29 22:07 ` redi at gcc dot gnu.org
  2022-11-06 17:24 ` pinskia at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: redi at gcc dot gnu.org @ 2020-11-29 22:07 UTC (permalink / raw)
  To: gcc-bugs

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |accepts-invalid
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2020-11-29

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug c++/98052] Allocation with new and deallocation with std::allocator should result in an error
  2020-11-29 15:35 [Bug c++/98052] New: Allocation with new and deallocation with std::allocator should result in an error src at andyf dot de
  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
  1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2022-11-06 17:24 UTC (permalink / raw)
  To: gcc-bugs

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
             Status|NEW                         |RESOLVED

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Dup of bug 95797.

*** This bug has been marked as a duplicate of bug 95797 ***

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-11-06 17:24 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-29 15:35 [Bug c++/98052] New: Allocation with new and deallocation with std::allocator should result in an error src at andyf dot de
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

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).