-
Notifications
You must be signed in to change notification settings - Fork 19
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
Build failure with corrupted test-triggers--usdt-tst-special.o
#98
Comments
I've seen this too, mostly when doing parallel builds of things doing dtrace -G, but never managed to track it down. I wonder if the problem is that dtrace -G modifies its inputs, as well as its outputs, so if you run dtrace -G with the same set of inputs twice at the same time... oh dear. Except you just ruled that out. It must be something else... |
diffing the two trees with native+expanded, I at least managed to kill the native dependency and cvised the flags down a bit (didn't go too far because of #100):
Not very insightful but it's better than "native fails". Pretty sure the flags can be reduced more and that it ended up getting stuck because of bad combinations. More later... |
I'm hitting it on my main workstation now with |
(Please don't spend time on this yet as I don't really feel like I've got a clear idea of how to reproduce it or why this environment is triggering it.)
I hit this build failure via the ebuild which failed like (with a debug print added):
Broken
or
Hacky debugging patch
Working
What I don't get yet is:
-j1
-g
-march=native
to-march=icelake-server -mabm -mno-pconfig -mno-sgx --param=l1-cache-line-size=64 --param=l1-cache-size=48 --param=l2-cache-size=49152
makes it work?This is with
gcc version 15.0.0 20240826 (experimental) 92c5265d22afaac146b2a7ecbc3dac9fc3382877 (Gentoo 15.0.9999 p, commit 24f7b8a07ce29ac39d8d3245a1ba7f7abf3dcfa1)
but I reproduced it with GCC 14 and 13 too.The text was updated successfully, but these errors were encountered: