COMP: circumvent aggressive compiler branch optimization (clang-17)
- it seems that both sides of the ternary are evaluated despite the divide-by-zero protection. Use volatile to force the compiler to use in-order evaluation.
Showing
- src/OpenFOAM/meshes/meshShapes/edge/edgeI.H 4 additions, 5 deletionssrc/OpenFOAM/meshes/meshShapes/edge/edgeI.H
- src/OpenFOAM/meshes/meshShapes/face/faceI.H 4 additions, 4 deletionssrc/OpenFOAM/meshes/meshShapes/face/faceI.H
- src/OpenFOAM/meshes/primitiveShapes/line/lineI.H 4 additions, 0 deletionssrc/OpenFOAM/meshes/primitiveShapes/line/lineI.H
- src/OpenFOAM/meshes/primitiveShapes/triangle/triangleI.H 4 additions, 4 deletionssrc/OpenFOAM/meshes/primitiveShapes/triangle/triangleI.H
- src/OpenFOAM/primitives/Vector/VectorI.H 3 additions, 0 deletionssrc/OpenFOAM/primitives/Vector/VectorI.H
- src/OpenFOAM/primitives/VectorSpace/VectorSpaceI.H 3 additions, 0 deletionssrc/OpenFOAM/primitives/VectorSpace/VectorSpaceI.H
- src/OpenFOAM/primitives/complex/complexI.H 1 addition, 0 deletionssrc/OpenFOAM/primitives/complex/complexI.H
- src/OpenFOAM/primitives/quaternion/quaternion.H 2 additions, 2 deletionssrc/OpenFOAM/primitives/quaternion/quaternion.H
- src/OpenFOAM/primitives/quaternion/quaternionI.H 5 additions, 4 deletionssrc/OpenFOAM/primitives/quaternion/quaternionI.H
- src/finiteArea/faMesh/faMeshDemandDrivenData.C 1 addition, 0 deletionssrc/finiteArea/faMesh/faMeshDemandDrivenData.C
Please register or sign in to comment