public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114275] using std::thread within a templated function in a module fails to compile Date: Tue, 07 May 2024 01:39:21 +0000 [thread overview] Message-ID: <bug-114275-4-3YwBMcA1Cu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114275-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114275 --- Comment #10 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Nathaniel Shead <nshead@gcc.gnu.org>: https://gcc.gnu.org/g:ec2365e07537e8b17745d75c28a2b45bf33be119 commit r15-220-gec2365e07537e8b17745d75c28a2b45bf33be119 Author: Nathaniel Shead <nathanieloshead@gmail.com> Date: Fri May 3 19:36:17 2024 +1000 c++/modules: Fix dangling pointer with imported_temploid_friends I got notified by Linaro CI and by checking testresults that there seems to be some occasional failures in tpl-friend-4_b.C on some architectures and standards modes since r15-59-gb5f6a56940e708. I haven't been able to reproduce but looking at the backtrace I suspect the issue is that we're adding to the 'imported_temploid_friend' map a decl that is ultimately discarded, which then has its address reused by a later decl causing a failure in the assert in 'set_originating_module'. This patch fixes the problem by ensuring 'imported_temploid_friends' is correctly marked as a GTY root, and that 'duplicate_decls' properly removes entries from the map for declarations that it frees. PR c++/114275 gcc/cp/ChangeLog: * cp-tree.h (remove_defining_module): Declare. * decl.cc (duplicate_decls): Call remove_defining_module on to-be-freed newdecl. * module.cc (imported_temploid_friends): Mark as GTY root... (init_modules): ...and allocate from ggc. (trees_in::decl_value): Only track for declarations that won't be discarded. (remove_defining_module): New function. Signed-off-by: Nathaniel Shead <nathanieloshead@gmail.com> Reviewed-by: Jason Merrill <jason@redhat.com> Reviewed-by: Patrick Palka <ppalka@redhat.com>
next prev parent reply other threads:[~2024-05-07 1:39 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-08 2:04 [Bug c++/114275] New: " michael.kenzel at gmail dot com 2024-03-08 2:19 ` [Bug c++/114275] " pinskia at gcc dot gnu.org 2024-03-08 3:15 ` nshead at gcc dot gnu.org 2024-03-08 15:09 ` ppalka at gcc dot gnu.org 2024-03-08 15:23 ` law at gcc dot gnu.org 2024-03-17 9:02 ` nshead at gcc dot gnu.org 2024-03-18 15:33 ` ppalka at gcc dot gnu.org 2024-04-30 6:23 ` cvs-commit at gcc dot gnu.org 2024-04-30 7:31 ` nshead at gcc dot gnu.org 2024-05-06 11:51 ` adhemerval.zanella at linaro dot org 2024-05-06 16:35 ` pinskia at gcc dot gnu.org 2024-05-07 1:39 ` cvs-commit at gcc dot gnu.org [this message] 2024-05-24 14:17 ` cvs-commit at gcc dot gnu.org 2024-05-24 14:18 ` nshead at gcc dot gnu.org 2024-06-01 2:10 ` nshead 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-114275-4-3YwBMcA1Cu@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: linkBe 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).