#2392: default values of keyword parameters are not checked to be in the allowed set
Reporter: Roland Haas
Status: open
Milestone:
Version:
Type: bug
Priority: major
Component: Cactus
Changes (by Roland Haas):
assignee: Steven R. Brandt (was )
responsible: [] (was )
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2392/default-values-of…
#2392: default values of keyword parameters are not checked to be in the allowed set
Reporter: Roland Haas
Status: open
Milestone:
Version:
Type: bug
Priority: major
Component: Cactus
Changes (by Roland Haas):
status: open (was new)
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2392/default-values-of…
#2392: default values of keyword parameters are not checked to be in the allowed set
Reporter: Roland Haas
Status: new
Milestone:
Version:
Type: bug
Priority: major
Component: Cactus
Comment (by Steven R. Brandt):
On looking into this, I see that there are some serious bugs here. Working on a fix.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2392/default-values-of…
#2595: Modern Intel compilers struggle to compile McLachlan resulting in extremely long build times
Reporter: Gabriele Bozzola
Status: new
Milestone:
Version: development version
Type: bug
Priority: minor
Component:
Comment (by Erik Schnetter):
The usual remedy is to reduce the optimization level for that particular file. This is, of course, not really a good idea since that file contains one of the most expensive routines.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2595/modern-intel-comp…
#2595: Modern Intel compilers struggle to compile McLachlan resulting in extremely long build times
Reporter: Gabriele Bozzola
Status: new
Milestone:
Version: development version
Type: bug
Priority: minor
Component:
Comment (by Gabriele Bozzola):
My understanding is that it does the opposite of what I want: it lets the compiler try as much to optimize as it wants \([https://www.intel.com/content/www/us/en/develop/documentation/cpp-compiler-developer-guide-and-reference/top/compiler-reference/compiler-options/compiler-option-details/advanced-optimization-options/qoverride-limits-qoverride-limits.html](https://www.intel.com/content/www/us/en/develop/documentation/cpp-compiler-developer-guide-and-reference/top/compiler-reference/compiler-options/compiler-option-details/advanced-optimization-options/qoverride-limits-qoverride-limits.html)\)
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2595/modern-intel-comp…
#2595: Modern Intel compilers struggle to compile McLachlan resulting in extremely long build times
Reporter: Gabriele Bozzola
Status: new
Milestone:
Version: development version
Type: bug
Priority: minor
Component:
Comment (by Steven R. Brandt):
Did you experiment with setting `-qoverride-limits`\` ?
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2595/modern-intel-comp…
#2595: Modern Intel compilers struggle to compile McLachlan resulting in extremely long build times
Reporter: Gabriele Bozzola
Status: new
Milestone:
Version: development version
Type: bug
Priority: minor
Component:
Comment (by Gabriele Bozzola):
<div class="preview-container wiki-content"><!-- loaded via ajax --></div>
<div class="mask"></div>
</div>
</div>
</form>
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2595/modern-intel-comp…
#2595: Modern Intel compilers struggle to compile McLachlan resulting in extremely long build times
Reporter: Gabriele Bozzola
Status: new
Milestone:
Version: development version
Type: bug
Priority: minor
Component:
As mentioned in ET Call on 09/02/22.
I am compiling a subset of the latest release of the Einstein Toolkit with one of latest version available of Intel oneAPI \(2021.5\). I am attaching thornlist and optionfile.
I see warnings like this:
```
/home/sbozzolo/storage/codes/einstein_toolkit/Cactus/configs/sim/build/ML_BSSN/ML_BSSN_EvolutionInteriorSplitBy2.cc(49): warning #16219: Some OpenMP processing was skipped to constrain compile time. Consider overriding limits (-qoverride-limits).
```
which essentially informs me that the compiler cannot optimize the code within a time frame that is heuristically determined.
As a result, compilation takes a very long time \(several tens of minutes\). I have seen this on other supercomputers with compilers from 2019.
\(I don’t seem able to attach two files, so I am attaching only the option list. \)
attachment: generic-intel.cfg (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2…)
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2595/modern-intel-comp…
#2364: avoid opening and closing HDF5 files multiple times during output
Reporter: Roland Haas
Status: open
Milestone:
Version:
Type: enhancement
Priority: minor
Component:
Comment (by Roland Haas):
I did some work during the hackathon. Will have to rework it a bit for a cleaner implementation, maybe add a parameter as well.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2364/avoid-opening-and…
#2254: let Cactus thorns register citation requests at runtime
Reporter: Roland Haas
Status: open
Milestone:
Version:
Type: enhancement
Priority: minor
Component: EinsteinToolkit thorn
Comment (by Roland Haas):
Was worked on during hackathon. Will check back in a month.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2254/let-cactus-thorns…