public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "psmith at gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109720] -Wmaybe-uninitialized triggering when I can see no path that would allow it
Date: Thu, 04 May 2023 13:23:05 +0000	[thread overview]
Message-ID: <bug-109720-4-2JUpVneCkq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109720-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Paul Smith <psmith at gnu dot org> ---
I'm happy to provide the source for DynamicBitSet (it's basically a union of a
uint64_t and a boost::dynamic_bitset so that if you have <=64 bits you use the
uint64_t and if you have >64 bits you use boost::dynamic_bitset).  I have a
hacked-up version of the original that removes all the unnecessary methods and
also throws away some of the complexity for handling the small bitset leg of
the union, which is not used in this example.

Providing the Boost stuff is harder because, as I'm sure you're aware if you've
used Boost, it's a LOT of headers and they all include others, etc. :).  But I
can try to get the necessary headers, or Boost can be downloaded separately.

  parent reply	other threads:[~2023-05-04 13:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03 20:40 [Bug c++/109720] New: " psmith at gnu dot org
2023-05-03 20:56 ` [Bug tree-optimization/109720] " psmith at gnu dot org
2023-05-03 20:59 ` pinskia at gcc dot gnu.org
2023-05-03 21:39 ` psmith at gnu dot org
2023-05-03 21:58 ` pinskia at gcc dot gnu.org
2023-05-04 11:28 ` rguenth at gcc dot gnu.org
2023-05-04 13:23 ` psmith at gnu dot org [this message]
2023-05-15 21:44 ` psmith at gnu dot 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-109720-4-2JUpVneCkq@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).