Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] compiling clang with a obj/ dir"
2007 Jul 14
0
[LLVMdev] compiling clang with a obj/ dir
On Sat, 14 Jul 2007, Holger Schurig wrote:
> I can compile LLVM using with this method:
>
> svn co ...
> cd llvm
> ./configure ...
> make
>
> or with that one:
>
> svn co ...
> mkdir obj
> cd obj
> ../llvm/configure ...
> make
>
>
> How does the second method work with the new, experimental C
> compiler, "clang" ? The doc said that
2007 Jul 15
0
[LLVMdev] compiling clang with a obj/ dir
Holger Schurig wrote:
> compiler, "clang" ? The doc said that you put the clang sourcecode
> into llvm/tools/clang, change into this directory and simply
> enter "make". This seems to be not possible with the second
method, at
> least not in a way that separates sources and binaries.
I also did not succeed building clang in obj-dir.
Only after "mv
2007 Aug 16
2
[LLVMdev] Strange error of llvm-ld
Tomas,
Please file a bug for this. Attach the .o files and command line in
question.
Thanks,
Reid.
On Wed, 2007-08-15 at 23:22 +0200, Tomas Lindquist Olsen wrote:
> I think I have experienced this when more than one module contains
> definitions for the same values. ie. it should only be a declaration
> in one of them.
>
> On 8/15/07, Holger Schurig <hs4233 at
2007 Aug 15
3
[LLVMdev] Strange error of llvm-ld
I'm using llvm-ld from SVN r41106
When issueing the command
$ /usr/src/llvm/installed/bin/llvm-ld -v -stats -native -O1 -strip-all -o main \
.obj/conf.o .obj/configwriter.o \
-L/usr/share/qt3/lib -L/usr/X11R6/lib \
-lcrypto -lusb -lutil -lqt-mt -lXext -lX11 -lm -lpthread
I get this output:
Linking bitcode file '.obj/conf.o'
Linked in file '.obj/conf.o'
Linking
2007 Jul 25
3
[LLVMdev] Segment Register Use
I realize I am one of the few who uses the segment registers
(especially CS and DS) on the ia32 chips for example, and a definite
few with complete segregation models that rival specialized physical
processors...
GCC still fails to use these correctly and if your LLVM still depends
on either Generic or some of the RTL models they use in various
processor definitions, I express concern for
2007 Aug 15
0
[LLVMdev] Strange error of llvm-ld
I think I have experienced this when more than one module contains
definitions for the same values. ie. it should only be a declaration
in one of them.
On 8/15/07, Holger Schurig <hs4233 at mail.mn-solutions.de> wrote:
> I'm using llvm-ld from SVN r41106
>
> When issueing the command
>
> $ /usr/src/llvm/installed/bin/llvm-ld -v -stats -native -O1 -strip-all -o main \
>
2004 Aug 14
7
Free MOH MP3
Hello All,
Sorry to rehash a question I am sure has shown several time but I cannot
google up the answer from the lists.
Does anyone know where I can get some royalty free, cost free music for
my music on hold?
I saw someone's post several weeks ago that said that this exists at a
download site but I have not been able to find it.
Thanks!
Wiley Siler
-------------- next
2007 Jul 25
0
[LLVMdev] Fwd: Segment Register Use
fucking hell, listserv...
---------- Forwarded message ----------
From: "Wilfred L. Guerin" <wilfredguerin at gmail.com>
Date: Wed, 25 Jul 2007 10:54:46 -0500
Subject: Re: [LLVMdev] Segment Register Use
To: Holger Schurig <hs4233 at mail.mn-solutions.de>
I was very much expecting this style of response ;)
I believe the following characteristics and class of example should
2008 May 30
1
[LLVMdev] PATCH: -dry-run option for llvmc2
This implements -dry-run for llvmc2:
$ llvmc2 -dry-run main.c
llvm-g++ -c -x c main.c -o /tmp/llvm_bGw2gN/main.bc -emit-llvm
llc -f /tmp/llvm_bGw2gN/main.bc -o /tmp/llvm_bGw2gN/main.s
llvm-gcc -c -x assembler /tmp/llvm_bGw2gN/main.s -o /tmp/llvm_bGw2gN/main.o
llvm-gcc /tmp/llvm_bGw2gN/main.o -o a.out
$ llvmc2 -dry-run -opt main.c
llvm-g++ -c -x c main.c -o /tmp/llvm_UGZtwL/main.bc -emit-llvm
opt
2006 Apr 19
3
[LLVMdev] 1.7 Pre-Release Ready for Testing
On 4/19/06, Patrick Meredith <pmeredit at uiuc.edu> wrote:
> I haven't seen anyone claim x86 linux objdir == srcdir, so I'll test it out.
> Missed the 18th,but I'll try to have it done asap.
>
>
> On Apr 18, 2006, at 2:51 PM, Robert L. Bocchino Jr. wrote:
> I'll test on Darwin/PPC, precompiled llvmgcc, objdir == srcdir.
>
> Rob
>
Sorry for being
2006 Apr 18
3
[LLVMdev] 1.7 Pre-Release Ready for Testing
I'll test on Darwin/PPC, precompiled llvmgcc, objdir == srcdir.
Rob
On Apr 16, 2006, at 1:42 PM, Chris Lattner wrote:
> On Sun, 16 Apr 2006, Tanya Lattner wrote:
>> For testing, we would like a mix of people to do x86 and ppc.
>> Please send email to the list if you plan to test, what
>> architecture, and if you will use the llvm-gcc binary or compile
>> it
2009 Apr 07
2
[LLVMdev] advice on default options for building LLVM-GCC on Ubuntu Linux
On Apr 5, 2009, at 7:13 AM, Duncan Sands wrote:
> On Saturday 04 April 2009 19:12:55 Mike Stump wrote:
>> On Apr 4, 2009, at 6:17 AM, Duncan Sands wrote:
>>> you need to use a separate objects directory and not build directly
>>> in the llvm-gcc tree. For some reason the Apple people placed a
>>> file
>>> GNUmakefile in the tree which
2007 May 15
8
[LLVMdev] 2.0 Pre-release tarballs online
I've uploaded the 2.0 pre-release to this location:
http://llvm.org/prereleases/2.0/
If you have free time and would like to help test this release, please
download the appropriate tarballs from the website.
Here are a few ways you can help test this release:
1) Download llvm-gcc4 binary and llvm. Compile and run make check.
2) Download llvm-gcc4 binary, llvm, and llvm-test. Compile, run
2001 Oct 14
2
Probelms with patching EXT-3
Hello anybody,
I have a Suse 7.2 Linux with Kernel 2.4.9, which is compiled by myself,
and is running stable.
Now I try to patch my sourcecode in the way you write on your homepage.
But thier are two Proglems:
1. When I download the the file "ext3-2.4-0.9.6-249.gz" with my Windows,
I get no packedfile, I get a Textfile?!
-so gunzip would not work.
2. never the less, I tried to patch
2006 Apr 19
0
[LLVMdev] 1.7 Pre-Release Ready for Testing
I haven't seen anyone claim x86 linux objdir == srcdir, so I'll test
it out. Missed the 18th,but I'll try to have it done asap.
On Apr 18, 2006, at 2:51 PM, Robert L. Bocchino Jr. wrote:
> I'll test on Darwin/PPC, precompiled llvmgcc, objdir == srcdir.
>
> Rob
>
> On Apr 16, 2006, at 1:42 PM, Chris Lattner wrote:
>
>> On Sun, 16 Apr 2006, Tanya Lattner
2007 Jul 23
2
[LLVMdev] Usage of /dev/null in makefiles wrong
/usr/src/llvm/llvm$ make
make: Warning: File `/dev/null' has modification time 4.9e+03 s
in the future
make[1]: Entering directory `/usr/src/llvm/llvm/lib/System'
...
At the end of the compilation it emits something about clock skew
detected.
The time of /dev/null on my box is weird because of udev and/or
time local settings. When it's created, the init scripts didn't
2009 Apr 07
4
[LLVMdev] advice on default options for building LLVM-GCC on Ubuntu Linux
On Tue, Apr 7, 2009 at 12:38 AM, Duncan Sands <baldrick at free.fr> wrote:
> Hi Bill,
>
>> We use GNUmakefile to trigger using the build_gcc script.
>
> thanks for the explanation, but I still don't understand why
> it is done this way. Why not just get Apple people to run some
> script, rather than trying to have "make" automagically do an
> Apple
2007 Aug 16
2
[LLVMdev] c const
On Thu, 16 Aug 2007, Holger Schurig wrote:
>> if the programmer is going to tell you that the memory pointed
>> to by a pointer argument is never written.
>
> There are ways to cast away a const.
You don't even need casts:
void foo(const int *P, int *Q) {
x = *P;
*Q = 1;
y = *P // redundant?
}
void bar() {
int X = 0;
foo(&X, &X);
}
-Chris
--
2015 Feb 10
4
[PATCH 0/1] update gnuefi to f64cef26
Updates the gnu-efi submodule to the latest version (f64cef26)
Changes to the gnu-efi makefiles require changes to the syslinux build
scripts. Mainly, the install targets dropped the $(SRCDIR) prefix, e.g.
- $(INSTALL) -m 644 $(SRCDIR)/elf_$(ARCH)_efi.lds $(INSTALLROOT)/$(LIBDIR)
+ $(INSTALL) -m 644 elf_$(ARCH)_efi.lds $(INSTALLROOT)/$(LIBDIR)
Since syslinux cd's to $(objdir)
2007 Jul 19
2
[LLVMdev] memory hog llvm-ld
> LLVM represents debug info as explicit calls to intrinsics.
> This approach has many advantages, but a possible disadvantage
> is that it can significantly increase the size of the bitcode.
> I don't know if that explains your observations. I'm curious
> to know how gcc stores debug info...
GCC stores debug info in ELF sections of the .o file, e.g.:
$ objdump -h wtd.o