[llvm-dev] big module for a project

Yuxi Chen via llvm-dev llvm-dev at lists.llvm.org
Fri Mar 11 18:54:42 PST 2016


Awesome.

Thanks,
Yuxi
________________________________
From: Tom Chen [cyt046 at gmail.com]
Sent: Friday, March 11, 2016 10:57 AM
To: Robinson, Paul
Cc: Yuxi Chen; llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev] big module for a project

Take a look at wllvm (https://github.com/travitch/whole-program-llvm)

2016-03-11 10:55 GMT-06:00 Robinson, Paul via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>>:
Maybe use llvm-link to collect the individual bitcode .o files into one master .o file, then your tool can load just the one big .o file.
--paulr

From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org<mailto:llvm-dev-bounces at lists.llvm.org>] On Behalf Of Yuxi Chen via llvm-dev
Sent: Thursday, March 10, 2016 7:55 PM
To: llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
Cc: llvmdev-bounces at cs.uiuc.edu<mailto:llvmdev-bounces at cs.uiuc.edu>; llvmdev at cs.uiuc.edu<mailto:llvmdev at cs.uiuc.edu>
Subject: [llvm-dev] big module for a project

Hi All,

I am using clang to compile Mysql source code. Because I want to do some inter-procedural analysis, hopefully, I want to get a .o(bitcode) file(a module) containing all possible function declarations and definitions. Is it possible to do that ? Or you guys have some suggestions?

To be clear, like Mysql, there is a mysqld routine, which is a major routine. I want to mysqld.o(which is generated by clang) to contain all possible function declarations and definitions. So when I do some analysis, I just need load one module, which is mysqld.o, instead of all .o files.


Best,
Yuxi

_______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160312/7c755e6f/attachment.html>


More information about the llvm-dev mailing list