-
Notifications
You must be signed in to change notification settings - Fork 438
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
Question about the time overhead of LLVMModuleSet::buildSymbolTable() #1573
Comments
Could you share us your bc file or provide a link to download? @jumormt could you take a look at this? |
@learjet5 Could you please send us the bitcodes that exhibit significant analyzing time differences? |
Thanks for your early reply! @yuleisui @jumormt I conducted experiments using It seems that the time overhead does not exhibit a linear relationship with the number of analyzed bc files. However, buildSymbolTable() in SVF-2.9 does indeed take more time. The difference is significant especially for 2600+ .bc files situation. Here are the shell commands and outputs of the above experiments (I added some debug output in the SVF code). |
Feel free to reach me if you need all the 2600+ .bc files of Linux-6.5-defconfig. |
Well, in SVF-2.8, the Thanks again for your help! |
@learjet5 thanks for reporting back. Could you help narrow down which part of ‘ inferObjType’ caused the issue? |
I'll try to look into it. If there are any updates, I'll let you know. |
I'm using SVF to analyze Linux kernel-6.5. The LLVM-version is 14.0.6. And the inputs include 2600+ .bc files.
At first, I'm using SVF-2.5 and everything goes well. It takes less than half an hour to build the PAG of the kernel code.
However, after I migrated the code to SVF-2.9, it takes more than 10 hours for the LLVMModuleSet::buildSymbolTable() step.
I know SVF has been refactored since SVF-2.6. But I didn't figure out why there can be such a large difference in time overhead between the two versions.
Thank you in advance for your response!
The text was updated successfully, but these errors were encountered: