similar to: [LLVMdev] Build Failure!

Displaying 20 results from an estimated 700 matches similar to: "[LLVMdev] Build Failure!"

2009 Dec 23
0
[LLVMdev] Build Failure!
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
2009 Oct 20
2
[LLVMdev] [cfe-dev] 2.6 pre-release2 ready for testing
On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >> To test clang: >> 1) Compile llvm and clang from source. > > LLVM fails to build for me on Cygwin. I get: > Does TOT build? If not, please file a bug. Unfortunately Cygwin is not in our release criteria. I'd like to have a buildbot running (if there is not one already) and then get someone to qualify it for the
2009 Oct 20
0
[LLVMdev] [cfe-dev] 2.6 pre-release2 ready for testing
> To test clang: > 1) Compile llvm and clang from source. LLVM fails to build for me on Cygwin. 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]:
2009 Oct 20
0
[LLVMdev] [cfe-dev] 2.6 pre-release2 ready for testing
2009/10/20 Tanya Lattner <lattner at apple.com>: > > On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: > >>> To test clang: >>> 1) Compile llvm and clang from source. >> >> LLVM fails to build for me on Cygwin. I get: >> > > Does TOT build? If not, please file a bug. No. Theres the runtime install bug (below), and llvm-gcc has a bug that I
2009 Oct 20
3
[LLVMdev] [cfe-dev] 2.6 pre-release2 ready for testing
On Oct 20, 2009, at 12:05 PM, Aaron Gray wrote: > 2009/10/20 Tanya Lattner <lattner at apple.com>: >> >> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >> >>>> To test clang: >>>> 1) Compile llvm and clang from source. >>> >>> LLVM fails to build for me on Cygwin. I get: >>> >> >> Does TOT build? If not,
2009 Oct 20
0
[LLVMdev] [cfe-dev] 2.6 pre-release2 ready for testing
2009/10/20 Tanya Lattner <lattner at apple.com>: > > On Oct 20, 2009, at 12:05 PM, Aaron Gray wrote: > >> 2009/10/20 Tanya Lattner <lattner at apple.com>: >>> >>> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >>> >>>>> To test clang: >>>>> 1) Compile llvm and clang from source. >>>> >>>> LLVM
2009 Aug 28
1
[LLVMdev] [Cygwin] 'make install' woes
I am getting the following on 'make install' on Cygwin both on debug and release builds :- llvm[3]: Installing Release /home/ang/llvm-coff/bin/llvmc.exe make[3]: Leaving directory `/home/ang/build/llvm-coff/tools/llvmc/driver' make[2]: Leaving directory `/home/ang/build/llvm-coff/tools/llvmc' make[1]: Leaving directory `/home/ang/build/llvm-coff/tools' make[1]: Entering
2009 Oct 17
12
[LLVMdev] 2.6 pre-release2 ready for testing
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,
2009 Sep 01
1
[LLVMdev] Problem building libprofile.
Hi, when I try to build libprofile with r80670 (both llvm and llvm-gcc) I get this error: make[1]: Entering directory `.../llvm-svn-debug-obj/runtime/libprofile' llvm[1]: Building Debug Bytecode Archive libprofile_rt.bca (internalize) llvm[1]: Installing Debug Shared Library /nfs/a5/astifter/astifter/llvm/llvm-svn-debug-obj/../llvm-svn-debug-install/lib/libprofile_rt.so 0 llvm-ld
2012 Jul 30
3
[LLVMdev] clean CMake build failing (Mac OS X 10.8)
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
2009 Aug 31
10
[LLVMdev] 2.6 pre-release1 ready for testing
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
2011 Apr 24
2
[LLVMdev] Problem with compiling the runtime libary
Hi Nick Thanks for you reply. CMAKE is very new to me. I complied using GNU WIN32 and got those errors. Is it possible to compile it using GNU WIN 32 and anything need to be modified? I managed to compile the run time library on a mac machine. Yafan On Fri, Apr 22, 2011 at 5:04 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > yafan zhao wrote: > >> Hi All >> Thanks for
2010 Dec 08
0
[LLVMdev] Reviewer for our Path Profiling Implementation
On Dec 3, 2010, at 11:21 AM, Adam Preuss wrote: > I am a student at the University of Alberta under the > supervision of José Nelson Amaral, and I have been working on > implementing path profiling into LLVM. I have completed my project > and would like to submit it. > > We are looking for a reviewer for the path profiling implementation. We > have sent previous requests
2010 Dec 08
1
[LLVMdev] Reviewer for our Path Profiling Implementation
Thank you for your suggestions on the patch. If the patch is committed, I would be willing to maintain it, though I am not sure what is all involved or how I am made aware of changes that need to be made. The technical report https://www.cs.ualberta.ca/system/files/tech_report/2010/PreussPathProfLLVM.pdf contains my benchmarks relating to profiling overhead in LLVM. Over the next week I will
2012 Mar 28
2
[LLVMdev] Building past few days with Clang++ and Clang produces errors on Cmake for Debian Linux
*System:* Debian Linux Sid/Unstable amd64 *LLVM/Clang:* Trunk *Scenario:* In the past couple of days I've been compiling against trunk I get two separate and spurious hang ups with CMake. *Note:* I build against more than just X86 follow along the progress of other platforms, though just building for X86 produces the same results below. *Assumption:* Configure cmake with prior built
2010 Dec 03
4
[LLVMdev] Reviewer for our Path Profiling Implementation
I am a student at the University of Alberta under the supervision of José Nelson Amaral, and I have been working on implementing path profiling into LLVM. I have completed my project and would like to submit it. We are looking for a reviewer for the path profiling implementation. We have sent previous requests to the llvmdev list but have so far been unsuccessful. Please see the attached
2009 Dec 08
2
[LLVMdev] LLVM 2.6 cygwin build fails
Hi, I'm trying to build LLVM 2.6 (from svn branch release_26) on cygwin 1.7, and I have the following errors with both GCC 3.4.4 and GCC 4.3.4 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 symbol __cygwin_dll_entry at 12; defaulting to 62fc1000
2013 Jan 03
4
[LLVMdev] Fatal error in build, include <utility> not found
I'm trying to customize llvm by adding a header file of my own and tweaking things accordingly. While building, things go well until a certain point where it stops seeing the includes of my file. I'm working on Ubuntu 12.04 with llvm-3.1 on a custom target (mips-like), gcc-4.6 and clang-3.2 (i've tried 3.1 too). >From what i've understood, when it builds the first binaries of
2017 Jan 02
2
RFC: Allowing @llvm.objectsize to be more conservative with null.
Hi George, On Mon, Jan 2, 2017 at 10:41 AM, George Burgess IV <george.burgess.iv at gmail.com> wrote: > Thanks for the comments! > >> Have you considered changing our existing behavior to match GCC's >> builtin_object_size instead of adding a new parameter > > Yup! My issue with turning `i1 %min` into `i8 %flags` is that > __builtin_object_size would get
2017 Jan 02
2
RFC: Allowing @llvm.objectsize to be more conservative with null.
Hi George, Have you considered changing our existing behavior to match GCC's builtin_object_size instead of adding a new parameter? That may be simpler overall. There's also a clear upgrade strategy -- fold every old style call to "<min> ? 0 : 1". You probably already know this, but GCC folds builtin_object_size(0, 0) to -1 and builtin_object_size(0, 2) to 0. We'll