search for: sguelton

On Mon, Mar 02, 2015 at 12:12:34AM -0500, John Criswell wrote: > On 3/2/15 12:07 AM, Haopeng Liu wrote: > >Got it, thanks. But in my pass, I use function name to locate. Can I > >disable mangling in clang? > > No, but you can probably fine a library that can either mangle the original > name or demangle the name you're seeing in the LLVM bitcode. > > As an FYI,

Hi Folks, Although LLVM now relies on cmake for its build configuration, it still calls an external Python script, namely llvm-build, to manage component dependecies, activation or deactivation of target componenents and generating description for llvm-config. This system is documented in http://llvm.org/docs/CommandGuide/llvm-build.html and https://llvm.org/docs/LLVMBuild.html. Several

...skipping tests of python3-only components when python3 isn't available, that seems entirely worthwhile, since we only need to do that once. On Tue, Dec 17, 2019, 7:43 AM Nico Weber via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Tue, Dec 17, 2019 at 5:12 AM Serge Guelton <sguelton at redhat.com> wrote: > >> At the beginning of the year, I've landed a large set of patches to >> support both Python 2 and Python3 in most Python scripts. Looks like I >> missed some of them :-) >> At that time, backward portability with Python2 was still relevant...

> >> You can look at AddOptimizationPasses() in opt.cpp. > > > > As far as I understand, the two passmanager do not interleave their > > passes. It first runs all the function passes and below. Then all the > > module passes. So if you specify: > > > > opt -mymodulepass0 -myfunctionpass -mymodulepass1 > > > > What you actually get is:

At the beginning of the year, I've landed a large set of patches to support both Python 2 and Python3 in most Python scripts. Looks like I missed some of them :-) At that time, backward portability with Python2 was still relevant, and I suspect it will still be the case for a few distributions that ship Python2 by default. That being said, Even RHEL8 uses Python3 by default, so at some point

...ailable, >> that seems entirely worthwhile, since we only need to do that once. >> >> >> >> On Tue, Dec 17, 2019, 7:43 AM Nico Weber via llvm-dev < >> llvm-dev at lists.llvm.org> wrote: >> >>> On Tue, Dec 17, 2019 at 5:12 AM Serge Guelton <sguelton at redhat.com> >>> wrote: >>> >>>> At the beginning of the year, I've landed a large set of patches to >>>> support both Python 2 and Python3 in most Python scripts. Looks like I >>>> missed some of them :-) >>>> At that time,...

Within the LLVM pass manager infrastructure, suppose we have two transformation passes, pass A makes some improvements, then pass B does likewise, but this creates opportunities for pass A to create further improvements (e.g. suppose B was function inlining) so it's desirable to run A again. How does the LLVM pass manager currently deal with this? -------------- next part -------------- An

...(-) ``` side effects are *not* unexpected, please let me know through [1] if you spot anything unusual related to LLVM components. -- Serge [1] https://reviews.llvm.org/D90848 [2] https://reviews.llvm.org/rG95537f450814c378fcb9d446dadcabc1385a5903 On Fri, Oct 9, 2020 at 6:51 PM Serge Guelton <sguelton at redhat.com> wrote: > Hi Folks, > > Although LLVM now relies on cmake for its build configuration, it still > calls an > external Python script, namely llvm-build, to manage component dependecies, > activation or deactivation of target componenents and generating > descri...

...we only need to do that once. >>>> >>>> >>>> >>>> On Tue, Dec 17, 2019, 7:43 AM Nico Weber via llvm-dev < >>>> llvm-dev at lists.llvm.org> wrote: >>>> >>>>> On Tue, Dec 17, 2019 at 5:12 AM Serge Guelton <sguelton at redhat.com> >>>>> wrote: >>>>> >>>>>> At the beginning of the year, I've landed a large set of patches to >>>>>> support both Python 2 and Python3 in most Python scripts. Looks like I >>>>>> missed some of...

Hi folks, Python2 has reached end of support[0], and many core Python packages are dropping pthon 2 support[1]. This is a subject that raises periodically on this mlist, with a rather strong no in 2018 [-1] and a slow move in 2019 [-2, -3]. Even if Python is not a core build requirement, it's used during some configurations steps (e.g. in the cmake export_executable_symbols function), for

Hi folks, I've been working for a few months on a proposal to make it easier to develop out-of-tree passes, and have them linked either statically or dynamically, within LLVM. This includes automatic integration within clang, opt and bugpoint. The goal is to lower the bar for people who develop out-of tree passes: they can maintain their code base in a third-party repo, pick it at config