Displaying 20 results from an estimated 200 matches similar to: "[LLVMdev] FreeBSD's 11.0-CURRENT contrib/llvm/include/llvm/ADT/IntrusiveRefCntPtr.h's IntrusiveRefCntPtr and its use violates C++ privacy rules"
2016 Oct 19
3
IntrusiveRefCntPtr vs std::shared_ptr
why llvm contains IntrusiveRefCntPtr instead of using only std::shared_ptr? IntrusiveRefCntPtr widely used in llvm and clang source code.
Due to better performance?
for example in main func of clang frontend:
int cc1_main(ArrayRef<const char *> Argv, const char *Argv0, void *MainAddr) {
ensureSufficientStack();
std::unique_ptr<CompilerInstance> Clang(new CompilerInstance());
2016 Oct 19
2
IntrusiveRefCntPtr vs std::shared_ptr
On Wed, Oct 19, 2016 at 9:31 PM, Mehdi Amini via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
>
> On Oct 19, 2016, at 11:14 AM, Bruce Hoult via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
> On Wed, Oct 19, 2016 at 6:24 PM, Benjamin Kramer via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>> In terms of performance shared_ptr has a number of
2016 Oct 19
4
IntrusiveRefCntPtr vs std::shared_ptr
On Wed, Oct 19, 2016 at 6:24 PM, Benjamin Kramer via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> In terms of performance shared_ptr has a number of disadvantages. One
> is that it always uses atomics even though most IntrusiveRefCntPtrs
> are used in single-threaded contexts. Another is weak_ptr adding a lot
> of complexity to the implementation, IntrusiveRefCntPtr
2020 Oct 01
2
OrcV1 removal
Hi,
On 2020-10-01 15:29:12 -0700, Lang Hames wrote:
> 24bytes / object -- Looks like I managed module ownership correctly but
> leaked the ThreadSafeModule container. This should be fixed in 5044196b412f.
That helped a bit, but not yet fully. Looks like it might be still
reachable memory, so leakcheck isn't that helpful.
Oooh. I think I see. For various reasons the symbol names we
2012 Jul 10
0
[LLVMdev] Unable to do even basic Clang tutorial
Hi Ashok,
$ cd bin/bin
$ ./llvm-config --ldflags --libs
-L/home/ubuntu/bin/lib -ldl -lpthread
-lLLVMAsmParser -lLLVMTableGen -lLLVMDebugInfo -lLLVMX86Disassembler -lLLVMX86AsmParser -lLLVMX86CodeGen -lLLVMSelectionDAG -lLLVMAsmPrinter -lLLVMX86Desc -lLLVMX86Info -lLLVMX86AsmPrinter -lLLVMX86Utils -lLLVMJIT -lLLVMMCDisassembler -lLLVMMCParser -lLLVMInstrumentation -lLLVMInterpreter
2012 Jul 10
2
[LLVMdev] Unable to do even basic Clang tutorial
You need to link in the libclang* as well.
On 7/10/2012 1:22 PM, NY Knicks Fan wrote:
> Hi Ashok,
>
> $ cd bin/bin
> $ ./llvm-config --ldflags --libs
> -L/home/ubuntu/bin/lib -ldl -lpthread
> -lLLVMAsmParser -lLLVMTableGen -lLLVMDebugInfo -lLLVMX86Disassembler
> -lLLVMX86AsmParser -lLLVMX86CodeGen -lLLVMSelectionDAG -lLLVMAsmPrinter
> -lLLVMX86Desc -lLLVMX86Info
2012 Jul 10
2
[LLVMdev] Unable to do even basic Clang tutorial
You will need to link to the LLVM/clang libraries. To get the correct
flags, you can run:
./llvm-config --ldflags --libs
and use the flags reported.
On 7/10/2012 11:35 AM, NY Knicks Fan wrote:
> OK. Thanks. I now get the following error (which appears to be a
> problem w/ the tutorial itself?):
>
> $ /home/ubuntu/bin/bin/clang++ -I /home/ubuntu/bin/include/
>
2012 Sep 21
2
[LLVMdev] Clang API parsing of the destructor
I am using the clang API (version 3.1 - trunk 153913) to compile some very simple code as follows
class MyClass
{
~MyClass() ;
};
MyClass::~MyClass()
{
}
int main()
{
return 0;
}
My problem is that I get the error message: test.cpp:20:10: error: destructor cannot have a return type MyClass::~MyClass()
If someone can point me to the right direction that would be great. It compiles fine if
2012 Jun 26
1
[LLVMdev] Error compiling llvm/clang with clang+libc++ with -std=cxx0x
Thanks Dimitry. That worked.
I see some warnings in my compilations:
> Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/IntEqClasses.cpp.o
> [ 2%] clang-3: warning: argument unused during compilation: '-nostdinc++'
> Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/IntrusiveRefCntPtr.cpp.o
> clang-3: warning: argument unused during compilation:
2012 Sep 21
0
[LLVMdev] Clang API parsing of the destructor
On Fri, Sep 21, 2012 at 12:22 PM, Kamaljit Lall <klall at factset.com> wrote:
> I am using the clang API (version 3.1 - trunk 153913) to compile some
> very simple code as follows****
>
> class MyClass
> {
> ~MyClass() ;
>
> };
>
> MyClass::~MyClass()
> {
>
> }
>
> int main()
> {
> return 0;
> } ****
>
> My problem is that
2012 Jul 10
0
[LLVMdev] Unable to do even basic Clang tutorial
OK. Thanks. I now get the following error (which appears to be a problem w/ the tutorial itself?):
$ /home/ubuntu/bin/bin/clang++ -I /home/ubuntu/bin/include/ -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS tutorial1.cpp/tmp/tutorial1-LQ71fW.o: In function `main':
tutorial1.cpp:(.text+0x42): undefined reference to `llvm::outs()'
tutorial1.cpp:(.text+0x72): undefined reference to
2020 Oct 02
2
OrcV1 removal
Hi Andres,
Ok -- I've added some API for this in 438db0719681: You can get the string
pool from the execution session
with LLVMOrcExecutionSessionGetSymbolStringPool, then clear that
with LLVMOrcSymbolStringPoolClearDeadEntries.
-- Lang.
On Thu, Oct 1, 2020 at 5:34 PM Lang Hames <lhames at gmail.com> wrote:
> Hi Andres,
>
> Oooh. I think I see. For various reasons the symbol
2012 May 29
1
[LLVMdev] [cfe-commits] r157260 - in /cfe/trunk: include/clang/Rewrite/Rewriter.h lib/Rewrite/Rewriter.cpp unittests/CMakeLists.txt unittests/Tooling/RewriterTest.cpp unittests/Tooling/RewriterTestContext.h
Manuel,
After the discussion at last night, I have agreed that
GetTemporaryDirectory() on Win32 would do bad thing, thank you.
dir = GetTemporaryDirectory();
dir.eraseFromDisk(erase_contents = true);
dir = GetTemporaryDirectory(); /* It doesn't create anything on Win32
due to caching */
I suppose Manuel wants GetTemporaryDirectory() to keep semantics
similar mkdtemp(3).
Though it is in
2020 Oct 01
2
OrcV1 removal
Hi,
On 2020-09-30 21:31:33 -0700, Lang Hames wrote:
> I've taken a first shot at hooking RTDyldObjectLinkingLayer up to the
> ResourceTracker API in 7436b2ab2428. Could you let me know whether that
> fixes the leak you were seeing?
It did improve the situation significantly, thanks!
There's still a smaller leak, unfortunately. The function comments for
modules say that:
/**
*
2012 Jul 10
3
[LLVMdev] Unable to do even basic Clang tutorial
Add -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS to your compilation flag.
On 7/10/2012 11:23 AM, NY Knicks Fan wrote:
> Hi Ashok,
>
> I created a new Ubuntu 12.04 virtual machine and followed directions
> except that I know use your cmake command instead of configure, and I
> got the error below.
>
> Any help is very much appreciated.
>
>
> $
2014 Jan 30
1
Asterisk 12 questions
Hi. I'm attempting to compile Asterisk 12, but we want to use chan_sip
instead of pjsip.
I am missing something. I assumed that chan_sip was going to be added by
default. Apparently not. I saw it in the menuconfig. Dumb question, but
double xx beside It..does that mean not avail/not going to be installed?
Can someone point me in the proper direction? A specific area where I can
learn to
2005 Feb 10
4
[ANNOUNCE] New stable release of Samba Console (1.1.23)
Hi,
I'm officialy announcing the new 1.1.23 stable release of Samba Console,
along with a stable IMC release too (1.2.24). This code is just going in
production at a new customer site this week.
From the project web site :
Samba Console <http://imc.sourceforge.net/samba/index.html> is the first
console developped for IMC. It offers a simple and ergonomic interface
for managing a
2013 Oct 03
0
[LLVMdev] libclang JIT frontend
Hi,
I'm not sure if this is a libclang, llvm::cl or clang-interpreter issue so I'll try posting here for a response.
I am using libclang as a frontend to the LLVM JIT (3.3 release). I started from the clang-interpreter example and have everything working (given a C/C++ source file I can have it JIT'd to memory and executed) for a single run. When I try to compile a second source
2017 Jun 28
2
Building llvm with clang and lld on arm and the llvm arm backend relocation on position independent code
> On 27 Jun 2017, at 13:25, Peter Smith <peter.smith at linaro.org> wrote:
>
> Hello Alessandro,
>
> Despite the statement in the HowToCrossCompileLLVM guide "If you’re
> using Clang as the cross-compiler, there is a problem in the LLVM ARM
> back-end that is producing absolute relocations on
> position-independent code (R_ARM_THM_MOVW_ABS_NC), so for now, you
2017 Jun 28
3
Building llvm with clang and lld on arm and the llvm arm backend relocation on position independent code
Oh, so it looks like I hit a bit of a wall there :-) I’ll take a look thanks.
That bug talks about R_ARM_THM_CALL which I assume are thumb related.
Will your implementation fix also R_ARM_CALL errors?
> On 28 Jun 2017, at 17:15, Peter Smith <peter.smith at linaro.org> wrote:
>
> Hello Alessandro,
>
> The LLD ARM port doesn't currently support range extension thunks,