-
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
Instruction Selection Deeply Recurses #1177
Comments
Can't reproduce on Linux. The input bytecode file generates a 3228 line x86 |
What format or encoding is the llc -debug log file in? |
Log is just plain bzip2 archive without any TAR'ing. The end look very suspicious:
0xe5c018
|
Looking at the --debug output on linux, yields some information:
So, I'm changing the topic of this to "Instruction Selection Deeply Recurses" I'll also attach the linux "llc --debug" output. |
Output from llc --debug on Linux |
There is potential loop in Select->SelectCode->Select_*->Select
The cheap workaround will be constructing objects in Select_ on heap, not on |
Yep. This is a known problem that is causing me considerable headache. Using a |
This is an important class of program that LLVM should handle without failing or Anton: what's the license for the .c file that you attached? Is it okay for us |
Reid! There is already a license header in the file:
So, I think it's ok to use source in tests. You might also take MD5 source code |
Sorry, as you can tell, I didn't even look at the code :) I just assumed it was raw. Thanks for cluing me in. Reid |
Fixed. |
mentioned in issue llvm/llvm-bugzilla-archive#851 |
Extended Description
Attached file caused llc to crash (llvm-gcc also). It seems to be insufficient
stack or something like this. Crash also occurs on md5.c code from libiberty.
I don't know the source of the problem and will investigate. Maybe this file
will crash llc on non-windows platform also.
Output from llc -debug is also attached. Just before crash I'm getting message like:
0075D433 (0x00000000 0x00000000 0x00000000 0x00000000)
The text was updated successfully, but these errors were encountered: