public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95797] Can std::allocator.deallocate newed pointer during constant evaluation
Date: Sun, 29 Aug 2021 00:36:18 +0000	[thread overview]
Message-ID: <bug-95797-4-oifJ32WQnW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95797-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to work|11.0                        |

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Clang has specific code to catch this:
<source>:4:5: error: static_assert expression is not an integral constant
expression
    (std::allocator<int>{}.deallocate(new int, 1),
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/compiler-explorer/clang-trunk-20210828/bin/../include/c++/v1/__memory/allocator.h:112:13:
note: 'std::allocator<...>::deallocate' used to delete pointer to object
allocated with 'new'
            ::operator delete(__p);
            ^
<source>:4:28: note: in call to '&std::allocator<int>{}->deallocate(&{*new
int#0}, 1)'
    (std::allocator<int>{}.deallocate(new int, 1),
                           ^
<source>:4:39: note: heap allocation performed here
    (std::allocator<int>{}.deallocate(new int, 1),
                                      ^

  parent reply	other threads:[~2021-08-29  0:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-21  3:14 [Bug c++/95797] New: " johelegp at gmail dot com
2020-06-21  8:59 ` [Bug c++/95797] " redi at gcc dot gnu.org
2021-08-29  0:20 ` johelegp at gmail dot com
2021-08-29  0:34 ` pinskia at gcc dot gnu.org
2021-08-29  0:35 ` pinskia at gcc dot gnu.org
2021-08-29  0:36 ` pinskia at gcc dot gnu.org [this message]
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-95797-4-oifJ32WQnW@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).