Peng Yu via llvm-dev
2019-Jan-13 05:44 UTC
[llvm-dev] Convert commands in make to llmv commands for code analysis
This URL mentions using LLVM IR to perform code analysis. https://stackoverflow.com/questions/9939794/how-to-use-llvm-to-generate-a-call-graph But the first problem to solve is how to convert the commands used in Makefiles to the corresponding LLVM commands. https://pastebin.com/RcnA14Qa The above URL shows the makefile screen output from the bash source code. Where `gcc -c`, `gcc` (link with -L -l), `ar` are used. Note that an archive (.a) file is created by combining many .o files in bash source code make output. However, LLVM does not have llvm-ld anymore. So there is no way to create a library file.Mising the ability to create an archive file in LLVM can cause trouble to mimic the compile flow using make. Does anybody have any good solution to this problem? -- Regards, Peng
Alberto Barbaro via llvm-dev
2019-Jan-13 07:08 UTC
[llvm-dev] Convert commands in make to llmv commands for code analysis
Hi Peng, Maybe you can install wllvm[1] and after use something like make CC=wllvm ? Thanks [1] https://github.com/travitch/whole-program-llvm On Sun, Jan 13, 2019, 06:44 Peng Yu via llvm-dev <llvm-dev at lists.llvm.org wrote:> This URL mentions using LLVM IR to perform code analysis. > > > https://stackoverflow.com/questions/9939794/how-to-use-llvm-to-generate-a-call-graph > > But the first problem to solve is how to convert the commands used in > Makefiles to the corresponding LLVM commands. > > https://pastebin.com/RcnA14Qa > > The above URL shows the makefile screen output from the bash source > code. Where `gcc -c`, `gcc` (link with -L -l), `ar` are used. > > Note that an archive (.a) file is created by combining many .o files > in bash source code make output. > > However, LLVM does not have llvm-ld anymore. So there is no way to > create a library file.Mising the ability to create an archive file in > LLVM can cause trouble to mimic the compile flow using make. > > Does anybody have any good solution to this problem? > > -- > Regards, > Peng > _______________________________________________ > LLVM Developers mailing list > 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/20190113/ef7ff266/attachment.html>
Peng Yu via llvm-dev
2019-Jan-13 12:10 UTC
[llvm-dev] Convert commands in make to llmv commands for code analysis
What about the AR make variable? On Sun, Jan 13, 2019 at 1:08 AM Alberto Barbaro <barbaro.alberto at gmail.com> wrote:> Hi Peng, > Maybe you can install wllvm[1] and after use something like make CC=wllvm ? > > Thanks > > [1] https://github.com/travitch/whole-program-llvm > > > > On Sun, Jan 13, 2019, 06:44 Peng Yu via llvm-dev <llvm-dev at lists.llvm.org > wrote: > >> This URL mentions using LLVM IR to perform code analysis. >> >> >> https://stackoverflow.com/questions/9939794/how-to-use-llvm-to-generate-a-call-graph >> >> But the first problem to solve is how to convert the commands used in >> Makefiles to the corresponding LLVM commands. >> >> https://pastebin.com/RcnA14Qa >> >> The above URL shows the makefile screen output from the bash source >> code. Where `gcc -c`, `gcc` (link with -L -l), `ar` are used. >> >> Note that an archive (.a) file is created by combining many .o files >> in bash source code make output. >> >> However, LLVM does not have llvm-ld anymore. So there is no way to >> create a library file.Mising the ability to create an archive file in >> LLVM can cause trouble to mimic the compile flow using make. >> >> Does anybody have any good solution to this problem? >> >> -- >> Regards, >> Peng >> > _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >> > --Regards, Peng -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190113/a2ee0ec5/attachment.html>