Hui Zhou
Hui Zhou
I see. This is a good conversation. The next layer of security is to control the specific port range to be used. You can use `MPIR_CVAR_PORTRANGE` for this purpose. This...
I am consolidating multiple tests, including `rma/fetch_and_op`, into a single test with command line parameters in https://github.com/pmodels/mpich/pull/5725. I'll make sure to guard the `long double` usage that PR.
Is there an archlinux package for ucx and could you try using that as a dependency? I believe mpich will use external ucx if detected.
> FFLAGS=-fallow-argument-mismatch \ > FCFLAGS=-fallow-argument-mismatch Also could you try without those flags? We have updated our fortran binding in 4.1 so that those flags are no longer necessary.
I believe `PTR` is just `void *`. It is probably an internal macro defined in one of the binutil headers that has gone away in the recent releases. Maybe PTR...
Solution 1: add configure option `--without-bfd`. UCX lose the ability of printing detailed backtrace (that I never find helpful) in case of segfaults. Solution 2: `sed -i -e 's/\/void */'...
https://github.com/openucx/ucx/pull/8450
The backtrace doesn't make sense -- how would `MPIR_Err_create_code -> MPII_Op_set_cxx -> MPII_Grequest_set_lang_f77 -> ucp_worker_create`? That is why I don't find ucx's backtrace ever useful. Simply try `gdb ./initnull` and...
Use `--enable-g=dbg` to add `-g` option to the compiler.
Nevertheless, they consistently point to the ucx stack during `Init`. We may get better luck escalating to the UCX folks.