Paige Weber

Hey Thomas! In case we have more problems with the google group and for the convenience of people reading this for the first time, I've included links to the code...

Thanks for the direction, I'll work on this and let you know if I have questions or progress

Hey Thomas, I feel like I'm in over my head trying to resolve this issue. I've looked at the code for several hours this week, but I think fixing this...

I'm happy to help with a tele/video conference. Perhaps it'd be best to email me to organize a time? My email is [email protected]

I noticed something today that might be a workaround. I added `#pragma omp barrier` immediately before the call to `likwid_markerNextGroup()` and after doing so I haven't seen a single case...

Hey Thomas! Sorry for the tardiness, seems like my email notifications aren't working. I will begin to use `likwid_markerNextGroup()` in sequential regions only. However, it seems that placing `#pragma omp...

Oh, okay! My mistake. I'll let you know if I encounter this issue again.

Well Thomas, it didn't take me long before I found this issue again :joy: I have been working on an updated example for `C-internalMarkerAPI.c`. You can see it [here](https://github.com/rileyweber13/likwid/blob/924836a2926fb21b70a7d34688645aa8de59aff6/examples/C-internalMarkerAPI.c). Just...

If I put all three regions inside a single for loop the problem goes away. [Here's updated code](https://github.com/rileyweber13/likwid/blob/616870e57a26423f9c6d65eb75b5da1b59732ecf/examples/C-internalMarkerAPI.c). However, this is significantly different from the original example code; is this...

Hey Tom! I saw this issue again today and thought my findings may be useful. Running the following command causes one or both of `DRAM_READS` and `DRAM_WRITES` to report 1.845e19....