Re: FW: ompd_get_thread_id in OMPD implementation

On Sat, Apr 09, 2022 at 12:38:11AM +0200, Ahmed Sayed Mousse wrote: > Sorry for the late reply. > I did check gomp_thread_self but I'm still not sure about what I should do, > maybe because I lack experience/knowledge. > Here is where my thinking is going right now and I hope you tell me if I'm > w

FW: ompd_get_thread_id in OMPD implementation

dge around this part. *From: *Ahmed Sayed Mousse *Sent: *Wednesday, March 23, 2022 7:23 PM *To: *gcc-h...@gcc.gnu.org *Cc: *ja...@redhat.com *Subject: *ompd_get_thread_id in OMPD implementation Hi everyone, I was doing a research to help me implement the function “ompd_get_thread_id” from the Op

ompd_get_thread_id() in OMPD implementation

Hi everyone, I was doing a research to help me implement the function “ompd_get_thread_id” from the OpenMP API specification under section 20.5.5.5. In this function I need to return a native thread identifier and from research I found that it’s a “pthread_t” handle which exists inside a struct

OMPD implementation

Hi, Can anyone of OpenMP contributors review my last patch? Thanks Mohamed

Re: GNU OMPD implementation

Hi, On 01.12.21 19:35, Martin Jambor wrote: On Tue, Nov 30 2021, Mohamed Atef wrote: Where is the variable of the OpenMP version defined? The GCC code itself does not make a difference, contrary to C/C++/Fortran which have -std= OpenMP 4.5 (also known as 201511) is fully supported (minus

Re: GNU OMPD implementation

Hi, On Tue, Nov 30 2021, Mohamed Atef wrote: > Hello, > for the gdb part it's already understood. gdb documentation explains > how to extend gdb functionality using python, and we looked at clang code > and now it's very clear how to provide OMPD functions with parameters. great to hear that

Re: GNU OMPD implementation

t;> sorry for replying this late, I'm looking into different things and my >> context switches are slow. >> >> On Wed, Nov 24 2021, Mohamed Atef wrote: >> > Hello everyone, >> > I need to remind you that we are working on implementation of OMPD, >> so

Re: GNU OMPD implementation

d Atef wrote: > > Hello everyone, > > I need to remind you that we are working on implementation of OMPD, > so > > you don't make it open for GSoC this year. > > I can assure you we will not accept an OMPD-implementation GSoC project, > because I consider it

Re: GNU OMPD implementation

C this year. I can assure you we will not accept an OMPD-implementation GSoC project, because I consider it just too big for effort of one individual. > > our progress so far, > We are working on a GDB extension using python so we can provide OMPD with > callbacks. > Jakub said tha

GNU OMPD implementation

Hello everyone, I need to remind you that we are working on implementation of OMPD, so you don't make it open for GSoC this year. our progress so far, We are working on a GDB extension using python so we can provide OMPD with callbacks. Jakub said that we need GDB support, but the GDB communit

GNU OMPD implementation

hello everyone, we read chapter 5 and the paper proposed RWTH Aachen University and the others They worked on the same project. some of us will work on OMPD, somebody will work on GDB plugin python script and somebody will work on GDB support as jakub said , but i have some clarifications that migh