Displaying 20 results from an estimated 20000 matches similar to: "[LLVMdev] User visible changes to llvmgcc and runtime libraries"
2004 Dec 12
2
[LLVMdev] LLVM_LIB_SEARCH_PATH
Chris Lattner wrote:
> On Sun, 12 Dec 2004, Reid Spencer wrote:
>
>> Hello,
>>
>> I need to solicit your opinion about something.
>>
>> I'm toying with the idea of getting rid of LLVM_LIB_SEARCH_PATH. Right
>> now the linkers will use this environment variable if it specifies a
>> single directory. It will look in that directory to find
2004 Dec 12
0
[LLVMdev] LLVM_LIB_SEARCH_PATH
On Sun, 12 Dec 2004, Reid Spencer wrote:
> Hello,
>
> I need to solicit your opinion about something.
>
> I'm toying with the idea of getting rid of LLVM_LIB_SEARCH_PATH. Right
> now the linkers will use this environment variable if it specifies a
> single directory. It will look in that directory to find libraries when
> things like -lc or -lcrtend are specified on
2004 Dec 13
2
[LLVMdev] LLVM_LIB_SEARCH_PATH
Chris Lattner wrote:
> On Sun, 12 Dec 2004, Jeff Cohen wrote:
>
>>> I definitely prefer #1. The only concern I have with it is that
>>> this makes it impossible to move the llvmgcc install directory once
>>> it is built (tools would not look in the correct directories).
>>>
>> This is a very big concern. Users of LLVM generally do not build
2004 Dec 12
5
[LLVMdev] LLVM_LIB_SEARCH_PATH
Hello,
I need to solicit your opinion about something.
I'm toying with the idea of getting rid of LLVM_LIB_SEARCH_PATH. Right
now the linkers will use this environment variable if it specifies a
single directory. It will look in that directory to find libraries when
things like -lc or -lcrtend are specified on the command line. Right
now, the only known place this is useful to set to is the
2003 Dec 02
0
[LLVMdev] Re: how to solve following question
Dear yueqiang,
I tracked this down this morning, and it is a bug with our Python code
that runs the tests. Essentially what is happening is that the code is
finding the temporary directory it created the first time it ran the
tests and believes that there are tests inside of it which it needs to
run. It then gets confused and quits.
This bug only shows up when the source tree and the
2003 Dec 05
0
[LLVMdev] Re: Makefile.config&setenv
yue wrote:
> hi,
> about [LLVMdev] another question
>
> thanks
>
> yueqiang
One other thing you might want to try is to put your object tree in a
directory that is *not* inside of your source tree. Currently, we don't
support using separate object trees that are subdirectories of the
source tree.
In other words:
Will work:
==========
SRC_ROOT=/home/yue/llvm
2003 Dec 07
0
[LLVMdev] Important change to LLVM makefiles
I have recently built the LLVM suite .. The problem is when I run
llvmgcc( after setting alias to $LLVM )
gcc: installation problem, cannot exec `gccld': No such file or directory
the LLVM_LIB_SEARCH_PATH=..
is set to LLVMGCCDIR/bytecode-libs
Any idea
2004 Sep 05
0
[LLVMdev] POST MORTEM: llvm-test changes
> That's weird. What is your default shell that Perl invokes with the
> "system" command. This works fine with bash-2.05b.
In reality :) i use this script in crontab (and run it manually with added
verbose flag):
---8X--------------
#!/bin/sh -
#
if !([ -d /home/wanderer/pkg/build/llvm/night/testresults-X86-FreeBSD ])
then mkdir
2004 Sep 05
2
[LLVMdev] POST MORTEM: llvm-test changes
Actually, I'm talking about the shell that Perl invokes. When you run
the NightlyTest.pl script, it uses Perl. The system() function in Perl
invokes the "standard" shell to execute the command provided as the
argument to system(). In NightlyTest.pl, I have changed the program to
check out both the regular llvm CVS module as well as the llvm-test
module. This command is what is
2004 Oct 27
2
[LLVMdev] Some Questions about LLVM
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=GB2312" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Yes, I checked that envvar, and it is set.<br>
The error msg when compiling a .c
2004 Dec 13
0
[LLVMdev] LLVM_LIB_SEARCH_PATH
On Sun, 12 Dec 2004, Jeff Cohen wrote:
>> I definitely prefer #1. The only concern I have with it is that this makes
>> it impossible to move the llvmgcc install directory once it is built (tools
>> would not look in the correct directories).
>>
> This is a very big concern. Users of LLVM generally do not build llvmgcc --
> are actively discouraged from building
2004 May 04
4
[LLVMdev] Plea for help
OK, details:
I run RH8 (gcc 3.2.something), RH9 (gcc 3.2.2-5) and Fedora.
Problems are the same across all setups. Hardware is Athlon 1600+
and half a giga RAM. Runs fail with an assertion when the linear
scan allocator is enabled, but runs without problems otherwise.
On RH9 (the system I have access to while generating this email) I
have the following details:
> 1) The LLVM assembly
2004 Dec 22
3
[LLVMdev] README: Build Environment Changes
LLVMers,
If you're not working from the CVS "head", you can ignore this.
Otherwise, please read it!
I have committed changes to CVS head that require changes to your build
environment. This is part of PR432. The changes involve getting the CFE
to build an executable named llvm-gcc instead of gcc. The hyphenated
name was chosen to be consistent with other LLVM tools, it is also
2004 Oct 25
0
[LLVMdev] Some Questions about LLVM
On Mon, 25 Oct 2004, zhou feng wrote:
> I have some questions about LLVM
> 1. I recently compiled LLVM on my X86 machine correctly. But when I use
> the built LLVm compiling programs(in the getting started guide), I got
> an warning saying can not find library "lc" (something like that). Yet
> LLVM did yeild a execution native code and it runs correctly except with
> a
2004 May 14
2
[LLVMdev] Can I disable the optimizaiton for llvmgcc?
Hi all LLVMor,
I just tried to compile a simple code and analyze the number of the basic blocks. But after compile, what I got, the bytecode is seems to be optimized bytecode. So the information of basic blocks is not what I expected. I want ot use the code as example to see how some of code optimization methods work. However, after compiling file using llvm test.c -o test, bytecode file
2005 May 18
0
LLVM 1.5 Release and Status Update!
The LLVM 1.5 is out! Get it here:
http://llvm.cs.uiuc.edu/releases/ or read about it here:
http://llvm.cs.uiuc.edu/releases/1.5/docs/ReleaseNotes.html#whatsnew
This release adds several new major features to the LLVM compiler, allows
it to be used in domains where it couldn't before (e.g. for functional
languages), supports new targets, generates faster code, and is much
easier to port
2004 Dec 20
3
[LLVMdev] Compiling FreeType 2.1.9 with LLVM 1.4
Adam,
I recant my previous message. I built FreeType with GCC not LLVMGCC by
accident (I shoulda checked!). The thing is, FreeType's makefiles don't
respect environment variables. So, I did this:
CC=/path/to/llvmgcc CXX=/path/to/llvmg++ configure
make
and was able to reproduce the problem. Not sure what's up with that but
as Misha pointed out, llvmgcc isn't any
2010 Nov 12
0
[LLVMdev] LLVM test-suite support for dragonegg / Fortran
Hi Tobias,
> I committed an extended version of that patch to llvm core and the test suite.
> Can you have a look, if it works for you.
if I configure like this then the configure script thinks llvm-gcc is not
dragonegg:
configure --with-llvmgcc="gcc-4.5 -fplugin=path/dragonegg.so"
--with-llvmgxx="g++-4.5 -fplugin=path/dragonegg.so"
There are several reasons for
2012 Feb 20
1
[LLVMdev] Building Test Suite Still Not Successful
Hello;
I am still having problems making the llvm-test suite and running command
like "make TEST=libcalls report" is giving me unexpected output. So first
I tried the following -
1. I built and installed llvm(3.0) under Ubuntu 11.10 (using the
./configure script found under llvm source, and then make and make
install). While configuring, I gave --prefix as a directory where I would
2004 Oct 25
5
[LLVMdev] Some Questions about LLVM
hi, all
I have some questions about LLVM
1. I recently compiled LLVM on my X86 machine correctly. But when I use
the built LLVm compiling programs(in the getting started guide), I got
an warning saying can not find library "lc" (something like that). Yet
LLVM did yeild a execution native code and it runs correctly except with
a waring saying something like "__main**"(I