search for: 293359

...n of a dump method should look like this: > #if !defined(NDEBUG) || defined(LLVM_ENABLE_DUMP) > LLVM_DUMP_METHOD void MyClass::dump() { > // print stuff to dbgs()... > } > #endif > > git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk at 293359 > 91177308-0d34-0410-b5e6-96231b3b80d8 > I would argue that removing dump() is the wrong thing to do even in Release builds. I am using LLVM as a JIT. In this use case, it is essential that one can inspect the IR at runtime. Perhaps in the AOT case dump() is not used in release versions but...

...this: > > #if !defined(NDEBUG) || defined(LLVM_ENABLE_DUMP) > > LLVM_DUMP_METHOD void MyClass::dump() { > > // print stuff to dbgs()... > > } > > #endif > > > > git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk at 293359 > > 91177308-0d34-0410-b5e6-96231b3b80d8 > > > > I would argue that removing dump() is the wrong thing to do even in > Release builds. I am using LLVM as a JIT. In this use case, it is > essential that one can inspect the IR at runtime. Perhaps in the AOT > case dump() is...

...if !defined(NDEBUG) || defined(LLVM_ENABLE_DUMP) >> > LLVM_DUMP_METHOD void MyClass::dump() { >> > // print stuff to dbgs()... >> > } >> > #endif >> > >> > git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk at 293359 >> > 91177308-0d34-0410-b5e6-96231b3b80d8 >> > >> >> I would argue that removing dump() is the wrong thing to do even in >> Release builds. I am using LLVM as a JIT. In this use case, it is >> essential that one can inspect the IR at runtime. Perhaps in the...

...M_ENABLE_DUMP) - The definition of a dump method should look like this: #if !defined(NDEBUG) || defined(LLVM_ENABLE_DUMP) LLVM_DUMP_METHOD void MyClass::dump() { // print stuff to dbgs()... } #endif git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk at 293359 91177308-0d34-0410-b5e6-96231b3b80d8 On Mon, Sep 25, 2017 at 1:22 PM, Dibyendu Majumdar via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi Martin > > On 25 September 2017 at 21:13, Martin J. O'Riordan <MartinO at theheart.ie> > wrote: > > Yes, if it is in the...

Hi Martin On 25 September 2017 at 21:13, Martin J. O'Riordan <MartinO at theheart.ie> wrote: > Yes, if it is in the interface it would make more sense to have a null implementation at the very least. In my out-of-tree target, I also removed them from the interface if the build was for Release to ensure that I got compile-time errors to reveal other places I might have otherwise

Hi, I am trying to make my axis labels left justified, and have used adj=0 in the axis() without success. Can anyone have a suggestion? axis(2,at=1:50,labels=paste('a',1:50,sep=''),las=2,cex.axis=0.5,adj=0,tck=0,mgp=c(3,0.5,0)) Thanks

...(LLVM_ENABLE_DUMP) > >> > LLVM_DUMP_METHOD void MyClass::dump() { > >> > // print stuff to dbgs()... > >> > } > >> > #endif > >> > > >> > git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk at 293359 > >> > 91177308-0d34-0410-b5e6-96231b3b80d8 > >> > > >> > >> I would argue that removing dump() is the wrong thing to do even in > >> Release builds. I am using LLVM as a JIT. In this use case, it is > >> essential that one can inspect the...

...afe code size. The dump methods can be included in the release builds anyway by enabling LLVM_ENABLE_DUMP. The actual implementation of this policy however lacked and depending on which dump() method you looked you would find a different pattern of when it is disable/enabled; I cleaned this up in r293359 <https://llvm.org/svn/llvm-project/llvm/trunk at 293359> so all dump methods are enabled/disabled consistenly. In any case if your client code uses dump() methods then I'd recommend to change it. - Matthias > >> >>> On Sep 25, 2017, at 11:40 AM, Dibyendu Majumdar vi...

Hi Matthias, On 25 September 2017 at 22:43, Matthias Braun <mbraun at apple.com> wrote: > The dump() methods are only meant to be used in debuggers and are only available in debug builds of LLVM. There are often similar print() methods available though. > I am not sure how this is the case seeing that the dump() function has been working in release builds in all the LLVM releases I