Re: [OMPI users] Issues compiling HPL with OMPIv4.0.0

Giles is correct. If mpicc is showing errors like those in your original email then it is not invoking a C compiler. C does not have any concept of try or catch. No modern C compiler will complain about a variable named “try” as it is not a reserved keyword in the C language. Example: foo.c:

Re: [OMPI users] Issues compiling HPL with OMPIv4.0.0

Do not get fooled by the symlinks to opal_wrapper ! opal_wrapper checks how it is invoked (e.g. check argv[0] in main()) and the behavior is different if it is invoked as mpicc, mpiCC, mpifort and other If the error persists with mpicc, you can manually extract the mpicc command line, and

Re: [OMPI users] Issues compiling HPL with OMPIv4.0.0

Sam and Jeff, Thank you for your answers. My first attempts actually used mpicc rather than mpiCC, switching to mpiCC was simply to check out if the problem persisted. I noticed that both mpicc and mpiCC are linked to the same file (opal_wrapper) and didn't bother switching it back. I'm not

Re: [OMPI users] Issues compiling HPL with OMPIv4.0.0

Indeed, you cannot use "try" as a variable name in C++ because it is a https://en.cppreference.com/w/cpp/keyword. As already suggested, use a C compiler, or you can replace "try" with "xtry" or any other non-reserved word. Jeff On Wed, Apr 3, 2019 at 1:41 PM Gutierrez, Samuel K. via users <

Re: [OMPI users] Issues compiling HPL with OMPIv4.0.0

Hi, It looks like you are using the C++ wrapper compiler (mpiCC) instead of the C wrapper compiler (mpicc). Perhaps using mpicc instead of mpiCC will resolve your issue. Best, Sam On Apr 3, 2019, at 12:38 PM, afernan...@odyhpc.com wrote: Hello, I'm trying to

Re: [OMPI users] Cannot catch std::bac_alloc?

OK. After help from several forums, I think I understand the cause of the problem. As Jeff said, it has nothing to do with MPI. Linux allows over committing (Thanks Joseph). See here and here

[OMPI users] Issues compiling HPL with OMPIv4.0.0

Hello, I'm trying to compile HPL(v2.3) with OpenBLAS and OMPI. The compilation succeeds when using the old OMPI (v1.10.8) but fails with OMPI v4.0.0 (I'm still not using v4.0.1). The error is for an old subroutine that determines machine-specific arithmetic constants: mpiCC -o HPL_dlamch.o -c

Re: [OMPI users] Cannot catch std::bac_alloc?

This is not an MPI problem. You will likely find StackOverflow to be a more effective way to get support on C++ issues. Jeff On Wed, Apr 3, 2019 at 8:47 AM Zhen Wang wrote: > Joseph, > > Thanks for your response. I'm no expert on Linux so please bear with me. > If I understand correctly,

Re: [OMPI users] Cannot catch std::bac_alloc?

Joseph, Thanks for your response. I'm no expert on Linux so please bear with me. If I understand correctly, using malloc instead of resize should allow me to handle out of memory error properly, but I still see abnormal termination (code is attached). I have more questions. 1. If the problem is

Re: [OMPI users] Cannot catch std::bac_alloc?

Zhen, The "problem" you're running into is memory overcommit [1]. The system will happily hand you a pointer to memory upon calling malloc without actually allocating the pages (that's the first step in std::vector::resize) and then terminate your application as soon as it tries to actually

[OMPI users] Cannot catch std::bac_alloc?

Hi, I have difficulty catching std::bac_alloc in an MPI environment. The code is attached. I'm uisng gcc 6.3 on SUSE Linux Enterprise Server 11 (x86_64). OpenMPI is built from source. The commands are as follows: *Build* g++ -I -L -lmpi memory.cpp *Run* -n 2 a.out *Output* 0 0 1 1