public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/106665] Cannot pass barrier by reference
       [not found] <bug-106665-4@http.gcc.gnu.org/bugzilla/>
@ 2022-10-09 13:51 ` phosit at autistici dot org
  2022-10-09 17:49 ` redi at gcc dot gnu.org
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 4+ messages in thread
From: phosit at autistici dot org @ 2022-10-09 13:51 UTC (permalink / raw)
  To: gcc-bugs

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

Phosit <phosit at autistici dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |phosit at autistici dot org

--- Comment #2 from Phosit <phosit at autistici dot org> ---
There is a race condition the threads in pool might access sync_point after
sync_point is destroyed.
If you swap the declarations the the threads in the pool are joined bevore
sync_point is destroyed

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

* [Bug libstdc++/106665] Cannot pass barrier by reference
       [not found] <bug-106665-4@http.gcc.gnu.org/bugzilla/>
  2022-10-09 13:51 ` [Bug libstdc++/106665] Cannot pass barrier by reference phosit at autistici dot org
@ 2022-10-09 17:49 ` redi at gcc dot gnu.org
  2022-10-10  2:39 ` shihyente at hotmail dot com
  2022-10-10  2:53 ` shihyente at hotmail dot com
  3 siblings, 0 replies; 4+ messages in thread
From: redi at gcc dot gnu.org @ 2022-10-09 17:49 UTC (permalink / raw)
  To: gcc-bugs

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I didn't see this when it got reported. It is definitely a race condition.
UBsan is telling you about a real bug in the program.

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

* [Bug libstdc++/106665] Cannot pass barrier by reference
       [not found] <bug-106665-4@http.gcc.gnu.org/bugzilla/>
  2022-10-09 13:51 ` [Bug libstdc++/106665] Cannot pass barrier by reference phosit at autistici dot org
  2022-10-09 17:49 ` redi at gcc dot gnu.org
@ 2022-10-10  2:39 ` shihyente at hotmail dot com
  2022-10-10  2:53 ` shihyente at hotmail dot com
  3 siblings, 0 replies; 4+ messages in thread
From: shihyente at hotmail dot com @ 2022-10-10  2:39 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #4 from SHIH YEN-TE <shihyente at hotmail dot com> ---
You are right, I didn't notice it as well. Thanks for pointing it out.

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

* [Bug libstdc++/106665] Cannot pass barrier by reference
       [not found] <bug-106665-4@http.gcc.gnu.org/bugzilla/>
                   ` (2 preceding siblings ...)
  2022-10-10  2:39 ` shihyente at hotmail dot com
@ 2022-10-10  2:53 ` shihyente at hotmail dot com
  3 siblings, 0 replies; 4+ messages in thread
From: shihyente at hotmail dot com @ 2022-10-10  2:53 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #5 from SHIH YEN-TE <shihyente at hotmail dot com> ---
Thanks, call pool.clear(); works.

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

end of thread, other threads:[~2022-10-10  2:53 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-106665-4@http.gcc.gnu.org/bugzilla/>
2022-10-09 13:51 ` [Bug libstdc++/106665] Cannot pass barrier by reference phosit at autistici dot org
2022-10-09 17:49 ` redi at gcc dot gnu.org
2022-10-10  2:39 ` shihyente at hotmail dot com
2022-10-10  2:53 ` shihyente at hotmail dot com

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