public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/103984] [12 regression] Possible maybe-uninitialized false positive on shaderc-2021.0 since r12-6329
Date: Tue, 01 Mar 2022 15:04:55 +0000	[thread overview]
Message-ID: <bug-103984-4-oKCFGmytzA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103984-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
Note I have a different test-case from benchmark package that show the same:

$ cat benchmark.ii
namespace std {
inline namespace __cxx11 {}
struct __new_allocator {
  void deallocate(char *, long) { operator delete(0); }
};
template <typename> using __allocator_base = __new_allocator;
template <typename> struct allocator_traits;
template <typename> struct allocator : __allocator_base<int> {};
template <typename _Tp> struct allocator_traits<allocator<_Tp>> {
  using allocator_type = allocator<_Tp>;
  using pointer = _Tp *;
  using size_type = long;
  static void deallocate(allocator_type __a, pointer __p, size_type __n) {
    __a.deallocate(__p, __n);
  }
};
} // namespace std
struct __alloc_traits : std::allocator_traits<std::allocator<char>> {};
namespace std {
template <class> struct initializer_list {
  int *_M_array;
  unsigned long _M_len;
};
namespace __cxx11 {
struct basic_string {
  struct _Alloc_hider : allocator_traits<allocator<char>> {
    pointer _M_p;
  } _M_dataplus;
  basic_string(const char *, const allocator<char> & = allocator<char>());
  ~basic_string() {
    if (_M_dataplus._M_p) {
      allocator<char> __trans_tmp_1;
      __alloc_traits::deallocate(__trans_tmp_1, 0, 1);
    }
  }
};
} // namespace __cxx11
} // namespace std
struct TestCase {
  std::basic_string name;
  bool error_occurred;
  std::basic_string error_message;
};
int AddCases(std::initializer_list<TestCase>);
int dummy68 = AddCases({{"", true, ""}});

  parent reply	other threads:[~2022-03-01 15:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11 22:18 [Bug c++/103984] New: [12 regression] Possible maybe-uninitialized false positive on shaderc-2021.0 slyfox at gcc dot gnu.org
2022-01-11 22:31 ` [Bug c++/103984] " pinskia at gcc dot gnu.org
2022-01-11 22:34 ` pinskia at gcc dot gnu.org
2022-01-12  7:39 ` rguenth at gcc dot gnu.org
2022-01-12  8:29 ` jakub at gcc dot gnu.org
2022-01-26 17:48 ` [Bug c++/103984] [12 regression] Possible maybe-uninitialized false positive on shaderc-2021.0 since r12-6329 jason at gcc dot gnu.org
2022-01-26 18:35 ` jason at gcc dot gnu.org
2022-01-26 19:03 ` jason at gcc dot gnu.org
2022-01-26 19:25 ` [Bug middle-end/103984] " jason at gcc dot gnu.org
2022-03-01 15:04 ` marxin at gcc dot gnu.org [this message]
2022-03-01 15:26 ` [Bug middle-end/103984] [12 regression] Possible maybe-uninitialized false positive on shaderc-2021.0 since r12-6329-g4f6bc28fc7dd86bd cvs-commit at gcc dot gnu.org
2022-03-15 14:22 ` jakub at gcc dot gnu.org
2022-03-15 15:06 ` jakub at gcc dot gnu.org
2022-03-15 15:16 ` jakub at gcc dot gnu.org
2022-03-15 15:55 ` jakub at gcc dot gnu.org
2022-03-15 16:55 ` jakub at gcc dot gnu.org
2022-03-15 18:00 ` jakub at gcc dot gnu.org
2022-03-16  8:47 ` jakub at gcc dot gnu.org
2022-03-16  8:58 ` jakub at gcc dot gnu.org
2022-03-17  8:26 ` cvs-commit at gcc dot gnu.org
2022-03-17  8:46 ` jakub 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-103984-4-oKCFGmytzA@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).