Closed Skroopa closed 3 months ago
What version of Jolt are you using? Can you check you have https://github.com/jrouwe/JoltPhysics/commit/178141555fe442af3209156bf4b7945ff521bf34?
latest master
and I can see -Wunused-parameter
, yes. Adding JPH_GCC_SUPPRESS_WARNING("-Wmaybe-uninitialized")
helps tho, and after further investigation I don't think we will have problems, if we will add it...
Sorry, I made a mistake: -Wunused-parameter
!= -Wmaybe-uninitialized
. I thought I had seen the same error before.
Adding JPH_GCC_SUPPRESS_WARNING("-Wmaybe-uninitialized")
will work indeed, but that turns off a useful warning completely. I've created a better fix here: #1159
I'm on GCC 14.0.1 and the warning doesn't trigger for me so I cannot test if this fixes it. Can you verify?
Also I'd be interested why it triggers for you. Which version of GCC are you using? With which flags are you building Jolt?
Yes, I found out that error with CollidingShape
occurs if INTERPROCEDURAL_OPTIMIZATION
is OFF
. The patch #1159 doesn't help to fix it. clang
version built without errors even if this flag is ON
.
USE_AVX
, USE_AVX2
, USE_AVX512
, USE_LZCNT
, USE_TZCNT
, USE_F16C
are OFF
and CROSS_PLATFORM_DETERMINISTIC
is ON
, g++
version 11.4.0 (part of build-essential
package).
I can reproduce it now. #1159 does fix the warning, but there are other similar warnings that trigger. I've globally disabled the warning now in #1166 and I'll merge it once it goes through the build.
Can't compile with
g++
on Ubuntu 22.04 in Docker:Any ideas how to fix this properly?