Displaying 20 results from an estimated 500 matches similar to: "[LLVMdev] Can't compile Apple's version on Linux"
2013 Feb 22
1
Issues with installing RBGL package
Hi all,
I was installing a package *RBGL* of bioconductor. However, I had some
issues while installing it. I asked the devel group of bioconductor and
they told me to consult this group. Here is my conversation with the
bioconductor group related to the problem
*Me->*
I was trying to install the RBGL package using the following command
biocLite("RBGL")
However, I got the
2009 Mar 05
0
[LLVMdev] Fwd: PPC Nightly Build Result
Hi Bill,
this might be a latent bug related to PPC. I have no such
machine to access atm., but I shall be able to reproduce the
problem when back at home. (In about 4 hours).
I keep you informed.
Cheers,
Gabor
On Mar 4, 7:57 pm, Bill Wendling <wendl... at apple.com> wrote:
> Something last night broke the build on Darwin PPC. Possible Gabor's
> check-in?
>
> -bw
2009 Mar 04
2
[LLVMdev] Fwd: PPC Nightly Build Result
Something last night broke the build on Darwin PPC. Possible Gabor's
check-in?
-bw
Begin forwarded message:
> From: admin at spang.apple.com (admin)
> Date: March 4, 2009 3:56:10 AM PST
> To: wendling at apple.com
> Subject: PPC Nightly Build Result
>
> /Volumes/SandBox/NightlyTest/llvmgcc42.roots/llvmgcc42~obj/obj-
> powerpc-powerpc/./prev-gcc/xgcc
2009 Nov 12
2
[LLVMdev] Bootstrap Failure
Hi all,
There's been a recent bootstrap failure that might be covered up
because of another failure. I just wanted to point this out so that
people can take a look:
-bw
Here's the failure from our buildbot:
Assertion failed: (DestReg == VirtReg && "Unknown load situation!"),
function RewriteMBB, file /Volumes/Sandbox/Buildbot/llvm/build.llvm-
2008 Feb 16
2
[LLVMdev] [llvm-testresults] Grawp-PIC i386 nightly tester results
>
> Using built-in specs.
> Target: i686-apple-darwin9
> Configured with: /tmp/llvmgcc42.r46865.roots/llvmgcc42.r46865~obj/
> src/configure --disable-checking --enable-werror --prefix=/Developer/
> usr/llvm-gcc-4.2 --mandir=/Developer/usr/llvm-gcc-4.2/share/man --
> enable-languages=c,objc,c++,obj-c++ --program-prefix=llvm- --program-
>
2013 Feb 22
0
Issues with installing RBGL package
Hi all,
I was installing a package *RBGL* of bioconductor. However, I had some
issues while installing it. I asked the devel group of bioconductor and
they told me to consult this group. Here is my conversation with the
bioconductor group related to the problem
*Me->*
I was trying to install the RBGL package using the following command
biocLite("RBGL")
However, I got the
2008 Feb 16
0
[LLVMdev] [llvm-testresults] Grawp-PIC i386 nightly tester results
On Feb 16, 2008, at 12:55 PM, Dale Johannesen wrote:
>>
>> Using built-in specs.
>> Target: i686-apple-darwin9
>> Configured with: /tmp/llvmgcc42.r46865.roots/llvmgcc42.r46865~obj/
>> src/configure --disable-checking --enable-werror --prefix=/Developer/
>> usr/llvm-gcc-4.2 --mandir=/Developer/usr/llvm-gcc-4.2/share/man --
>>
2008 Feb 16
0
[LLVMdev] [llvm-testresults] Grawp-PIC i386 nightly tester results
llvm itself is built with gcc-4.0, but the run line is:
// RUN: %llvmgxx -S -O0 -emit-llvm %s -o - | grep retval | grep S242 |
grep {i32 1} | count 2
According the log:
FAIL: /Volumes/Muggles/LLVM/nightlytest-pic/build/llvm/test/C+
+Frontend/2008-02-13-sret.cpp
Failed with exit(1) at line 1
while running: /usr/local/bin/llvm-gcc -emit-llvm -S -O0 -emit-llvm /
2011 Jan 13
2
[LLVMdev] About test suits
Hi sir,
I have built the test suits in following steps:
0. $cd LLVM_GCC_DIR; $gunzip --stdout llvm-gcc-4.2-*version*-*
platform*.tar.gz | tar -xvf -
1. $cd SRC_DIR/llvm-2.8/projects
2. $svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
3.$cd OBJ_DIR; 4. $SRC_DIR/configure --prefix=INS_DIR --enable-debug-runtime
--disable-optimized --enable-debug-symbols
2009 Mar 05
1
[LLVMdev] Fwd: PPC Nightly Build Result
FYI: It also showed up for ARM yesterday, but only for a non-debug
build.
On Mar 5, 2009, at 4:32 AM, Gabor Greif wrote:
> Hi Bill,
>
> this might be a latent bug related to PPC. I have no such
> machine to access atm., but I shall be able to reproduce the
> problem when back at home. (In about 4 hours).
>
> I keep you informed.
>
> Cheers,
>
> Gabor
>
2009 Jun 30
0
[LLVMdev] llvm-gcc-4.2 build failure: llvm-convert.cpp:‘ReplacementStrings’ may be used uninitialized in this function
g++ -m32 -c -g -O2 -mdynamic-no-pic -DIN_GCC -W -Wall -Wwrite-strings -
pedantic -Wno-long-long -Wno-variadic-macros -Wmissing-format-
attribute -Werror -mdynamic-no-pic -DHAVE_CONFIG_H -Wno-unused -
DTARGET_NAME=\"i686-apple-darwin9\" -DNDEBUG -I. -I. -I/tmp/
llvmgcc42.roots/llvmgcc42~obj/src/gcc -I/tmp/llvmgcc42.roots/
llvmgcc42~obj/src/gcc/.
2008 Feb 02
3
[LLVMdev] Problem Compiling llvm-gcc 4.2
>>
Dear All,
I have been trying for days but still cannot break this barrier. May I
get your help?
I have compiled llvm-2.1 successfully and make install. When I proceed
with llvm-gcc-4.2-2.1, however, I keep getting linking error as
attached. Some functions with totally different content conflict with
each other in linking process.
That is a Linux box (Debian, with 2.6.23-1
2008 Feb 16
2
[LLVMdev] [llvm-testresults] Grawp-PIC i386 nightly tester results
On Feb 16, 2008, at 11:32 AM, Evan Cheng wrote:
> But I am using llvm-gcc-4.2. Any idea why it's failing?
>
> Evan
All the failing testers are using gcc-4.0 according to the web pages
they point at.
> On Feb 16, 2008, at 11:24 AM, Dale Johannesen wrote:
>
>> On Feb 16, 2008, at 7:06 AM, Apache wrote:
>>> New Test Failures:
>>>
2011 Jan 14
0
[LLVMdev] About test suits
Please email the list, not me directly.
Try doing a 'make clean' then a 'make VERBOSE=1' in the test-suite directory.
-Chris
On Jan 13, 2011, at 6:04 PM, Qingan Li wrote:
> Hi Chris,
>
> [qali at qali SingleSource]$ llvm-gcc -v
> Using built-in specs.
> Target: x86_64-unknown-linux-gnu
> Configured with: /home/nicholas/2.8-final/llvmgcc42-2.8.src/configure
2012 Apr 25
2
[LLVMdev] Crash in JIT
Hello,
[Using LLVM r155315, according to `svn log | head`]
I am experimenting with programatically building and jitting functions in a module, and I seem to be coming across a crash in some generated code. Using the llvm-c interface I build up the module which dumps like this:
; ModuleID = 'MyModule'
target datalayout = "i686-apple-darwin11"
target triple =
2013 Feb 20
1
[LLVMdev] Temporally shutdown few clang-x86_64-darwin11 builders
Hello,
I am going temporally shutdown the next few builders for maintenance works:
clang-x86_64-darwin11-cross-mingw32
clang-x86_64-darwin11-self-mingw32
clang-x86_64-darwin11-cross-arm
Thank you for understanding.
Thanks
Galina
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2012 Apr 25
0
[LLVMdev] Crash in JIT
Hi David,
I'm not certain, but to me the "LLVMSetTarget(module, "i686-apple-darwin11");" line looks suspicious. I'm not familiar with all the ins and outs of how target triples get handled, but it looks to me like that's requesting 32-bit code.
I think that if you omit that line completely then the target will be inferred from the execution environment. My best
2010 Jul 05
0
[LLVMdev] likely SPECCPU2006 miscompilation
Using clang r107598 at -O1 to create reportable SPECINT 2006 results, I'm
getting the output below, which is almost certainly due to a
miscompilation. Known problem?
Thanks,
John
Running (#3) 403.gcc ref base i386-m32-gcc42-nn default
/home/regehr/z/specCPU2006/bin/specinvoke -d
/home/regehr/z/specCPU2006/benchspec/CPU2006/403.gcc/run/run_base_ref_i386-m32-gcc42-nn.0000
-e
2008 Feb 18
1
[LLVMdev] [llvm-testresults] Grawp-PIC i386 nightly tester results
On Feb 16, 2008, at 2:35 PM, Tanya Lattner wrote:
> On Feb 16, 2008, at 12:55 PM, Dale Johannesen wrote:
>>> Using built-in specs.
>>> Target: i686-apple-darwin9
>>> Configured with: /tmp/llvmgcc42.r46865.roots/llvmgcc42.r46865~obj/
>>> src/configure --disable-checking --enable-werror --prefix=/
>>> Developer/
>>> usr/llvm-gcc-4.2
2009 Jun 03
3
[LLVMdev] LLVM-gcc for Ada
Thanks for the suggestion, Andre. I downloaded GNAT GPL 2007, and
followed the directions on your web page. Now I get a lot of C++
errors. In fact, the output I captured to a log file is over six
megabytes just from the start of the problem command to the termination
of the make. I'm obviously not going to include it all here, but the
command and the first few errors are copied below.