Regarding PetscCall(). It sounds like you are working with two different versions of PETSc with different compilers? This isn't practical since things do change (improve we hope) with newer versions of PETSc. You should just built the latest version of PETSc with all the compiler suites you are interested in.
Barry > On Jun 27, 2023, at 11:32 AM, 冯上玮 <[email protected]> wrote: > > Hi, > > After failure with MS-MPI once and once again, I tried icl+oneAPI and > succeeded in installing and testing PESTc in Cygwin! > > However, (always however) when I copied the example code on Getting Started > page on visual studio, there are tons of error like: > <[email protected]> > I just wonder where the problem locates, I've googled this error message and > it seems that it's induced by the difference of compilers, c.f. > https://stackoverflow.com/questions/42136395/identifier-builtin-expect-is-undefined-during-ros-on-win-tutorial-talker-ex. > But Intel says that they also provide such thing on icl, and I actually use > this compiler instead of visual studio cl... > > Anyway, the project could be built if I delete these error-checking macro. > > Installing feedback (or as a test result): > When configure on windows, only icl + impi works, and in this case, both > --with-cc and --with-cxx options need to point out the version like: > --with-cc-std-c99 and --with-cxx-std-c++'ver'. Other combinations such as cl > + impi, icl + msmpi, cl + msmpi never work. My tutor told me that older > version of msmpi may work but I never try this. > > FENG.
