similar to: Soundness in clang SA

Thanks for the detailed explanation. So is changing the analysis technique from path sensitive (symbolic execution) analysis to some other technique bring in the soundness property ? Thanks, Siddharth On Sat, Aug 18, 2018 at 1:27 AM, Artem Dergachev <noqnoqneo at gmail.com> wrote: > Nope, at least not with the "path-sensitive" (symbolic execution) engine. > Which is the

We are currently implementing the backends for other solvers (you can follow the progress here: https://github.com/mikhailramalho/clang). So far we got Boolector, MathSAT and Yices ready. CVC4 should be done soon. When used to refute bugs, they all give roughly the same results: a ~5% speedup if there are refuted bugs or a ~5% slowdown if no bug is refuted. I've only tried to analyze one

Hi all, Currently studying the impact of SMT solvers on Clang SA. Can anyone help in telling more about the SMT solvers use in clang SA ? ( Have already tested Z3 SMT solver implemented in GSoC 2018 , also looking for other SMT solvers if possible ) Thanks, Siddharth -------------- next part -------------- An HTML attachment was scrubbed... URL:

+Aaron because i think he uses scan-build on Windows more or less successfully. I won't have time for setting up a Windows machine for myself in the nearest future. Could you tell us exactly what you're doing and what exactly does it print to console, more in the spirit of http://www.catb.org/~esr/faqs/smart-questions.html ? > scan-build: Not supported for windows. Exiting...

Hi Siddharth, alternativly you can try this <https://github.com/rizsotto/scan-build>, it's written in Python. Regards, Laszlo On Sat, Apr 6, 2019 at 5:14 AM Artem Dergachev via cfe-dev < cfe-dev at lists.llvm.org> wrote: > Hi, > > I never tried it myself but i can try to help you with specific problems > that you're having if you disclose them. > >

Hi Chris, Thanks for the suggestion i was trying to use the patch https://reviews.llvm.org/D30691 and ASTimporter concept for cross file analysis. Can u explain in details the approach u suggested ? What is `nm` on the object files ? Can u suggest some approach to start on this cross file analysis tool. Thanks, Siddharth On Tue, Sep 19, 2017 at 9:42 PM, Chris Bieneman <beanz at apple.com>

Hello, I am a computer science student new to LLVM compiler infrastructure. Please guide me where to start from to learn LLVM in the most effective way. Thanks, Siddharth Shankar Swain -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170115/6855d875/attachment.html>

Yes running LLVM performance test suite with LTO and Thin LTO enabled. Thanks, Siddharth On Fri, May 11, 2018 at 7:32 PM, Teresa Johnson <tejohnson at google.com> wrote: > I'm not completely sure what you are asking. Are you looking for > performance benchmarks to use for LTO and ThinLTO testing? Or are you > asking how to build/run with LTO and ThinLTO? Are you asking how to

Hi, Thanks for the info, If i only want to run performance test on benchmarks for LTO and Thin LTO enabled target, Can u suggest ways to do it ? I want to do it at my end. Thanks, Siddharth On Wed, May 2, 2018 at 7:03 PM, Teresa Johnson <tejohnson at google.com> wrote: > I've only measured performance on x86. There are some old results for SPEC > cpu2006 in the blog post here:

Hi Chris, Thanks for answering, Can u clarify on this comment mentioned in https://github.com/Z3Prover/z3/issues/861 . cplusplus no exception support · Issue #861 · Z3Prover/z3 · GitHub - LLVM's *source code* does not use exceptions for performance reasons and so is compiled by default with -fno-exceptions. When using LLVM's libraries via it's C++ interface it is important

> On Sep 19, 2017, at 10:09 AM, Siddharth Shankar Swain <h2015096 at pilani.bits-pilani.ac.in> wrote: > > Hi Chris, > Thanks for the suggestion i was trying to use the patch https://reviews.llvm.org/D30691 <https://reviews.llvm.org/D30691> and ASTimporter concept for cross file analysis. Can u explain in details the approach u suggested ? There is a tutorial on

Hi, Can anyone help if for example we have multiple c files and we want to analyze their ASTs to find out any dependency between them ( like a function defined in one c file is used in other, any external variable etc ). How can we do it at the AST level? I mean is there any automated tool or flag for it in LLVM. If anyone has any idea please tell. sincerely, Siddharth -------------- next part

Thanks. I am just trying to find a relocation and linking design for Hexagon architecture, whether to follow the MIPS style of relocation or other architecture style of relocation. Thats my question . Thats why i was asking about the functions and their differences Please guide. Thanks, Siddharth On Fri, Apr 21, 2017 at 8:37 PM, mats petersson <mats at planetcatfish.com> wrote: > If

Thanks for the reply. I was just asking about in general whatever header files are there in Targets/ for different architectures are not including any function except this processRelocationRef() to be used in RuntimeDyldELF.cpp or RuntimeDyldCOFF.cpp or RuntimeDyldMachO.cpp and i think these files are the ones which are actually doing the relocation and linking work. So what purpose do these

Hopefully someone else on the dev list who has experience with LNT and the LLVM test-suite will chime in. I've never run it myself. Adding Mehdi since he ran it with LTO/ThinLTO. I found some documentation for the test-suite: https://llvm.org/docs/TestingGuide.html#test-suite-overview http://llvm.org/docs/lnt/quickstart.html http://llvm.org/docs/lnt/tests.html#llvm-cmake-test-suite But I

Thanks for reply, it was really helpful. Can u just be more specific and tell about processRelocationRef() and resolveRelocation() in Targets/RuntimeDyld(objectfile format)(arch).h and also in RuntimeDyldELF.cpp and how the same function is implemented in different ways in both the files ? Thanks, Siddharth On Thu, Apr 20, 2017 at 8:16 PM, mats petersson <mats at planetcatfish.com> wrote:

yeah so when LTO runs, in the linker, it uses the target to produce object code. In the sense of code generation for target arch. Thanks, Siddharth On Mon, Jan 29, 2018 at 11:03 PM, Teresa Johnson <tejohnson at google.com> wrote: > Can you be more specific? LTO/ThinLTO are target independent. You just > need to be using a linker that supports *LTO (gold, lld, ld64, eg). > Teresa

I'm not completely sure what you are asking. Are you looking for performance benchmarks to use for LTO and ThinLTO testing? Or are you asking how to build/run with LTO and ThinLTO? Are you asking how to run LLVM's performance test-suite with LTO and ThinLTO? Teresa On Fri, May 11, 2018 at 5:21 AM Siddharth Shankar Swain < h2015096 at pilani.bits-pilani.ac.in> wrote: > Hi, >

Hi all, Can anyone explain why exceptions are disabled in LLVM, even if some C++ coding standard tells to use exceptions ? Thanks, Siddharth -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180501/ed7903db/attachment-0001.html>

Hi, Can anyone guide on how to enable LTO and Thin LTO for a new backend target ? Thanks, Siddharth -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180129/2ae8f38d/attachment.html>