-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
[predsimplify] release run works fine, debug run goes crazy #1339
Comments
Could it be a wonky assert? Did you try Release+Asserts build? Reid. |
entirely possible. No I didn't try. |
I tried the testcase under valgrind and it didn't show any memory errors. That |
Given that predsimplify is being rewritten, the problem doesn't reproduce on |
Perhaps when predsimplify is rewritten. Until then, we can't verify it. -Chris |
updated to current bytecode format |
This is done. |
Extended Description
This is a nasty bug that points to some memory corruption issue or something.
time ~/llvm/Release/bin/opt -predsimplify -disable-output bugpoint-reduced-simplified.bc
0.055u 0.009s 0:00.06 83.3% 0+0k 0+1io 0pf+0w
time ~/llvm/Debug/bin/opt -predsimplify -disable-output bugpoint-reduced-simplified.bc
Note that the .bc does have a large nasty cfg, but it is strange that this issue should only affect a
debug opt and not a release opt. This points to some memory clobbering, or deleting something, but
not removing it from a map or something (i.e. it's address is still the key or value of some map).
I'm disabling predsimplify in llvm-gcc until this is resolved, this breaks debug bootstraps on both ppc
and x86.
-Chris
The text was updated successfully, but these errors were encountered: