#2714: PAPI fails to build on Linux systems
Reporter: Roland Haas
Status: new
Milestone: ET_2023_05
Version:
Type: bug
Priority: major
Component:
Comment (by Roland Haas):
@{557058:1671c5c3-29cc-4e83-9850-a152d33a6235} says \(in pull request\) “Looks good to me.”
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2714/papi-fails-to-bui…
#2717: conflicting barriers in CarpetLib
Reporter: Roland Haas
Status: new
Milestone:
Version:
Type: bug
Priority: minor
Component: Carpet
To debug some Cactus issues on the Delta cluster I am running simulations using:
```
CarpetLib::barriers = "yes"
CarpetLib::barrier_between_stages = "yes"
Carpet::barriers = "yes"
Carpet::schedule_barriers = "yes"
Carpet::sync_barriers = "yes"
```
which results in failure:
```
WARNING level 0 from host cn045.delta.internal.ncsa.edu process 47
while executing schedule bin CCTK_RECOVER_VARIABLES, routine IOUtil::IOUtil_RecoverGH
in thorn CarpetLib, file /scratch/rhaas/Cactus/arrangements/Carpet/CarpetLib/src/dist.cc:210:
-> Wrong id for Barrier "CarpetLib::gdata::gdata": expected 783988953d, found 404924393d
exec: /scratch/rhaas/Cactus/arrangements/Carpet/Carpet/src/helpers.cc:275: int Carpet::Abort(const _cGH
*, int): Assertion `0' failed.
```
I expect this will be avoidable if I reduce the number of barriers used, so is not a major issue.
The two barriers involved \(based on their tags\) are the one in the `gdata::gdata` constructor and `commstate::step` “CarpetLib::comm\_state::step”.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2717/conflicting-barri…
#2663: add an notice about minimum Intel / GCC version required to configure output
Reporter: Roland Haas
Status: new
Milestone:
Version:
Type: enhancement
Priority: major
Component:
Comment (by Roland Haas):
There is no strict version check one could do. Eg gcc-4.8 on my debian box compiles the ET fine, but gcc-4.8 on an old RedHat based cluster fails. Either Debian includes some fixes in gcc or it is due to more modern system include files. In any case, _sometimes_ even gcc-4.8 is fine, but not always.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2663/add-an-notice-abo…
#2663: add an notice about minimum Intel / GCC version required to configure output
Reporter: Roland Haas
Status: new
Milestone:
Version:
Type: enhancement
Priority: major
Component:
Comment (by Zach Etienne):
Sure, but where is the PR?
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2663/add-an-notice-abo…