search for: commonprofiling

...directory `/home/foad/llvm/objdir-2.6/runtime' > make[2]: Entering directory `/home/foad/llvm/objdir-2.6/runtime/ > libprofile' > llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC) > llvm[2]: Compiling BlockProfiling.c for Release build (PIC) > llvm[2]: Compiling CommonProfiling.c for Release build (PIC) > llvm[2]: Compiling EdgeProfiling.c for Release build (PIC) > llvm[2]: Compiling FunctionProfiling.c for Release build (PIC) > llvm[2]: Linking Release Loadable Module profile_rt.dll > /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: > w...

...I get: make[1]: Entering directory `/home/foad/llvm/objdir-2.6/runtime' make[2]: Entering directory `/home/foad/llvm/objdir-2.6/runtime/libprofile' llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC) llvm[2]: Compiling BlockProfiling.c for Release build (PIC) llvm[2]: Compiling CommonProfiling.c for Release build (PIC) llvm[2]: Compiling EdgeProfiling.c for Release build (PIC) llvm[2]: Compiling FunctionProfiling.c for Release build (PIC) llvm[2]: Linking Release Loadable Module profile_rt.dll /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: warning: cannot find entry...

...ad/llvm/objdir-2.6/runtime' >> make[2]: Entering directory `/home/foad/llvm/objdir-2.6/runtime/ >> libprofile' >> llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC) >> llvm[2]: Compiling BlockProfiling.c for Release build (PIC) >> llvm[2]: Compiling CommonProfiling.c for Release build (PIC) >> llvm[2]: Compiling EdgeProfiling.c for Release build (PIC) >> llvm[2]: Compiling FunctionProfiling.c for Release build (PIC) >> llvm[2]: Linking Release Loadable Module profile_rt.dll >> /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwi...

...untime' >>> make[2]: Entering directory `/home/foad/llvm/objdir-2.6/runtime/ >>> libprofile' >>> llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC) >>> llvm[2]: Compiling BlockProfiling.c for Release build (PIC) >>> llvm[2]: Compiling CommonProfiling.c for Release build (PIC) >>> llvm[2]: Compiling EdgeProfiling.c for Release build (PIC) >>> llvm[2]: Compiling FunctionProfiling.c for Release build (PIC) >>> llvm[2]: Linking Release Loadable Module profile_rt.dll >>> /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../...

...>> make[2]: Entering directory `/home/foad/llvm/objdir-2.6/runtime/ >>>> libprofile' >>>> llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC) >>>> llvm[2]: Compiling BlockProfiling.c for Release build (PIC) >>>> llvm[2]: Compiling CommonProfiling.c for Release build (PIC) >>>> llvm[2]: Compiling EdgeProfiling.c for Release build (PIC) >>>> llvm[2]: Compiling FunctionProfiling.c for Release build (PIC) >>>> llvm[2]: Linking Release Loadable Module profile_rt.dll >>>> /usr/lib/gcc/i686-pc-cygwin...

...ing.c:(.text+0xe8): undefined reference to `_atexit' /cygdrive/c/projects/thesis/llvm-suite-2.6/llvm-2.6/runtime/libprofile/Release/BlockProfiling.o:BlockProfiling.c:(.text+0x65): undefined reference to `_atexit' /cygdrive/c/projects/thesis/llvm-suite-2.6/llvm-2.6/runtime/libprofile/Release/CommonProfiling.o:CommonProfiling.c:(.text+0x76): undefined reference to `_strdup' /cygdrive/c/projects/thesis/llvm-suite-2.6/llvm-2.6/runtime/libprofile/Release/CommonProfiling.o:CommonProfiling.c:(.text+0x9a): undefined reference to `_memmove' /cygdrive/c/projects/thesis/llvm-suite-2.6/llvm-2.6/runtime/l...

...tools' make[1]: Entering directory `/home/ang/build/llvm-coff/runtime' make[2]: Entering directory `/home/ang/build/llvm-coff/runtime/libprofile' llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC) llvm[2]: Compiling BlockProfiling.c for Release build (PIC) llvm[2]: Compiling CommonProfiling.c for Release build (PIC) llvm[2]: Compiling EdgeProfiling.c for Release build (PIC) llvm[2]: Compiling FunctionProfiling.c for Release build (PIC) PIC seems to be enabled for some strange reason, even with --disable-pic on configure. Then there seems to be a missing library too :- llvm[2]: Link...

This is a new build failure as of today. Does this look familiar to anyone? -bw llvm[2]: Compiling CommonProfiling.ll to CommonProfiling.bc for Debug build (bytecode) Intrinsic parameter #1 is wrong! i64 (i8*, i32)* @llvm.objectsize.i64 Intrinsic parameter #1 is wrong! i64 (i8*, i32)* @llvm.objectsize.i64 Intrinsic parameter #1 is wrong! i64 (i8*, i32)* @llvm.objectsize.i64 Intrinsic parameter #1 is wrong! i64...

My mistake. I needed to update llvm-gcc as well. Sorry for the noise. -bw On Dec 23, 2009, at 3:22 PM, Bill Wendling wrote: > This is a new build failure as of today. Does this look familiar to anyone? > > -bw > > llvm[2]: Compiling CommonProfiling.ll to CommonProfiling.bc for Debug build (bytecode) > Intrinsic parameter #1 is wrong! > i64 (i8*, i32)* @llvm.objectsize.i64 > Intrinsic parameter #1 is wrong! > i64 (i8*, i32)* @llvm.objectsize.i64 > Intrinsic parameter #1 is wrong! > i64 (i8*, i32)* @llvm.objectsize.i64 > In...

LLVMers, 2.6 pre-release2 is ready to be tested by the community. http://llvm.org/prereleases/2.6/ If you have time, I'd appreciate anyone who can help test the release. To test llvm-gcc: 1) Compile llvm from source and untar the llvm-test in the projects directory (name it llvm-test or test-suite). Choose to use a pre- compiled llvm-gcc or re-compile it yourself. 2) Run make check,

Over the weekend I upgraded my system to Mac OS X 10.8, and now a clean cmake build fails. The error message: > Building C object runtime/libprofile/CMakeFiles/profile_rt-static.dir/CommonProfiling.c.o > cc1: error: unrecognized command line option "-Wcovered-switch-default" The configuration: > Mac OS X 10.8 > CMake 2.8.8 > LLVM tot > Apple clang version 4.0 (tags/Apple/clang-421.0.57) (based on LLVM 3.1svn) Running cmake to generate the make files gives the foll...

LLVMers, 2.6 pre-release1 is ready to be tested by the community. http://llvm.org/prereleases/2.6/ You will notice that we have quite a few pre-compiled binaries (of both clang and llvm-gcc). We have identified several bugs that will be fixed in pre-release2, so please search the bug database before filing a new bug. If you have time, I'd appreciate anyone who can help test the

Hi! I did manage to load phone with SIP image : SIP70.8-0-3S, made SEP-MAC.cnf.xml, but phone never read the configuration from it. On the screen it's written "Unprovisioned", and phone is not trying to register with asterisk. Please help!! MihaelaMJ -------------- next part -------------- An HTML attachment was scrubbed... URL:

continuing discussions of 79xx issues. i've seen referenced and am experiencing difficulty getting a 7970 to work behind NAT to a public asterisk server. i am successful with 7960s. 1. SIP load is 70.8-3-3SR2S 2. config works fine if 7970 is connecting to an asterisk server a local LAN (same subnet) 3. when debugging it in a NAT'd environment I see the register and

Hi, ? We are new to IP phone firmware upgradation (Sorry if it is a re-post of previous question(s)). ? Recently we have bought a cisco 7942G IP phone. It currently has SIP 42.9-0-2SR1S firmware loaded on it. We do not see any option to configure a SIP Proxy where we can provide SIP Server (Asterisk PC/Device)? IP address (with current firmware on it) to register it with Asterisk. ? Do we need to

Anyone have the 7970 xml config for sip yet? Aaron

Hi, I have been using Cisco 7960's with Asterisk for years. I am trying get a 7961 working and have a problem. In my configuration, not all of my line appearances register to the same Asterisk SIP server. I have an Asterisk server at home and another at work. My Line 1 button registers to the home server and my Line 2 button registers to the work server. This has worked for years

...vn/runtime/libprofile/exported_symbols.lst -o .../llvm-svn-debug-obj/runtime/libprofile/Debug/profile_rt.internalize .../llvm-svn-debug-obj/runtime/libprofile/Debug/BasicBlockTracing.bc .../llvm-svn-debug-obj/runtime/libprofile/Debug/BlockProfiling.bc .../llvm-svn-debug-obj/runtime/libprofile/Debug/CommonProfiling.bc .../llvm-svn-debug-obj/runtime/libprofile/Debug/EdgeProfiling.bc .../llvm-svn-debug-obj/runtime/libprofile/Debug/FunctionProfiling.bc .../llvm-svn-debug-obj/runtime/libprofile/Debug/OptimalEdgeProfiling.bc make[1]: *** [.../llvm-svn-debug-obj/Debug/lib/libprofile_rt.bca] Segmentation fault make[...

Hi Everyone, I am having some issues getting my 7961 working with Trixbox. I have loaded the SIP code (8-3-3SR2) fine but when the phone boots up it goes into an unprovisioned state. A status message shows up and says ?Error Verifying Config Info?. I have read quite a bit on this topic (getting 7961?s to work with Asterisk and TB) and only came across a few postings where other people

...xt llvm-2.9.new/runtime/libprofile/CMakeLists.txt --- llvm-2.9/runtime/libprofile/CMakeLists.txt 1970-01-01 08:00:00.000000000 +0800 +++ llvm-2.9.new/runtime/libprofile/CMakeLists.txt 2011-04-24 15:41:56.549409372 +0800 @@ -0,0 +1,8 @@ +add_llvm_loadable_module( profile_rt + BasicBlockTracing.c + CommonProfiling.c + PathProfiling.c + EdgeProfiling.c + OptimalEdgeProfiling.c + Profiling.h + )