From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) by sourceware.org (Postfix) with ESMTPS id 9BDAC385841F for ; Mon, 7 Mar 2022 17:57:31 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 9BDAC385841F Received: by mail-wm1-x333.google.com with SMTP id bi14-20020a05600c3d8e00b00386f2897400so6090250wmb.5 for ; Mon, 07 Mar 2022 09:57:31 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BP5ftSiiE7nM8bFInxzmHifevQgWtkyjgFHA+rICh2s=; b=R1VGYLE98ATabYJtHI0vYKx8xA8QR/E3tjJBOdoao039cWH+niVMoqzc6D/LJBEaTN ioeEIKx0jw0OZpLTMUnt161jNsgXh+uX0WrUV+2DWCn+UjN5O6Mq1jV56J+D7/re5pMx GJMks/dgEECz6SmxIBK2RKU9aJSZA61fuRjp+ydGrt/VHEodnep8pUS9gPAyfwumdZZ4 iePqxBNG78sV2P26sisJ6BjMfqcvb1K8JT1RbrScrPa+R7chSv7g4VLod/V96hxP9N2T MJTPnEPdGOUH8wlTKHoSm0xDiHYxjezok5lWFHljY1KeOGJG6vmGhMibG0CQV6Ef7jhy Bdgw== X-Gm-Message-State: AOAM532yE0phV/ypKf+NljTi03xqZiiu8/wTXpogHBaOlaYf3Yv6VxdK Q7m9fpCPfLH3kL7e2Ak07GpvIPZD83FUj1+1mZk= X-Google-Smtp-Source: ABdhPJws4gj/+6fsslQcV0AbT5Ddb4wWG+BvX9gMWs03+jinPLk/72eUjWs2qBWXrvYdVpOkVzBvG2uTIfzn6Pj1Z34= X-Received: by 2002:a05:600c:3541:b0:389:95b2:5f63 with SMTP id i1-20020a05600c354100b0038995b25f63mr91997wmq.126.1646675850470; Mon, 07 Mar 2022 09:57:30 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Mohamed Atef Date: Mon, 7 Mar 2022 19:57:19 +0200 Message-ID: Subject: Re: Beginning OpenMP Threads To: Martin Jambor Cc: gcc@gcc.gnu.org X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2022 17:57:33 -0000 Hi, Thanks a lot. The good news is that by the end of this month I think we will finish most of OMPD. The remaining parts need OMPT support which is missing in GNU but all the other functions work perfectly fine. Finished work, Initialization Thread handles ICVs remaining work, task handles parallel region handles Thanks Mohamed On Mon, Mar 7, 2022 at 7:40 PM Martin Jambor wrote: > Hi, > > it's been a while since I had a serious look into libgomp... > > On Fri, Feb 25 2022, Mohamed Atef via Gcc wrote: > > Hello everyone, > > From OpenMP specs. > > "The OpenMP implementation must execute ompd_bp_thread_begin at every > > native-thread-begin and initial-thread-begin event. This execution occurs > > before the thread starts > > the execution of any OpenMP region" > > > > "When terminating an OpenMP thread, the implementation executes > > ompd_bp_thread_end." > > > > are these team_start and team_end in team.c file? > > ...but - based on a rather quick look - while I think you correctly > tracked down that gomp_team_start is the place actually creating the > threads, I think that the OMPD implementation wants to execute the > ompd_bp_thread_begin function for each thread and by the native > (pthread) thread. And, as far as I can tell, that seems to be the > function gomp_thread_start. At the moment I cannot quite tell if the > end of the function would be a good place for the thread termination > event - or rather if it is sufficient and there may be others, I would > need to dig deeper. But perhaps this already help? > > Martin > >