-
Notifications
You must be signed in to change notification settings - Fork 521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The gcc-12 build is failing due to FbgemmSparseDenseInt8Avx2. : ‘mask_int32_v’ may be used uninitialized [-Werror=maybe-uninitialized] #1666
Comments
Hi @jayagami, thanks for reporting this issue! Currently, our offiicial build instructions specify gcc 10, because it supports the lowest common denominator in terms of glibc and glibcxx versions on older Linux distributions (namely Ubuntu 20.04 and CentOS 7). Since these errors appear to be just uninitialized-variable errors, we will fix within the next few days (currently we are backlogged with other developments). In the meantime, we recommend building inside a Conda environment, in which you can install a local version of gcc 10 (see our full build instructions here). Please let us know if you have any questions or concerns. |
This uninitialized variable issue is being addressed with #1697. However, this alone will not fix the build because there a known regression in GCC 12 (see here). To work around that, you will need to add the following to your environment prior to re-running CMake: export CFLAGS+=" -Wno-error=maybe-uninitialized -Wno-error=uninitialized -Wno-error=restrict"
export CXXFLAGS+=" -Wno-error=maybe-uninitialized -Wno-error=uninitialized -Wno-error=restrict" |
Thanks, that's great to hear, it's not a serious problem, but I think it's better to report. |
Closing this issue, as we have added a note to the build instructions in the README, which should unblock users trying to build FBGEMM on gcc-12. Feel free to re-file a ticket if the issue is blocking your builds. |
With recent gcc, fbgemm doesn't build with -Wmaybe-uninitialized and upstream recommends building with -Wno-error=maybe-uninitialized pytorch#1666 https://pytorch.org/FBGEMM/fbgemm-development/BuildInstructions.html PyTorch itself uses -Wno-maybe-uninitialized but this doesn't get passed through to fbgemm.
Failed with gcc12, passed with gcc11
Error:
Env:
The text was updated successfully, but these errors were encountered: