Displaying 20 results from an estimated 40 matches for "parallel_dir".
Did you mean:
parallel_dirs
2008 Nov 20
2
[LLVMdev] Patch to VMKIT tools makefile
...h fixes that.
Index: tools/Makefile
===================================================================
--- tools/Makefile (revision 59726)
+++ tools/Makefile (working copy)
@@ -8,11 +8,12 @@
##=
=
=----------------------------------------------------------------------
===##
LEVEL = ..
-PARALLEL_DIRS = vmkit vmjc
+PARALLEL_DIRS = vmkit
include $(LEVEL)/Makefile.config
ifeq ($(WITH_JNJVM), 1)
+ PARALLEL_DIRS += vmjc
PARALLEL_DIRS += jnjvm
endif
Bye,
Deano
2010 Mar 04
4
[LLVMdev] Cygwin patches for 2.7
...em :)
Aaron
Index: tools/Makefile
===================================================================
--- tools/Makefile (revision 97136)
+++ tools/Makefile (working copy)
@@ -44,4 +44,8 @@
DIRS := $(filter-out lto gold, $(DIRS))
endif
+ifeq ($(TARGET_OS), $(filter $(TARGET_OS), Cygwin))
+ PARALLEL_DIRS := $(filter-out edis, $(PARALLEL_DIRS))
+endif
+
include $(LEVEL)/Makefile.common
Index: runtime/Makefile
===================================================================
--- runtime/Makefile (revision 97136)
+++ runtime/Makefile (working copy)
@@ -20,8 +20,12 @@
PARALLEL_DIRS := $(filter-out...
2008 Nov 20
0
[LLVMdev] Patch to VMKIT tools makefile
...===================================================
> --- tools/Makefile (revision 59726)
> +++ tools/Makefile (working copy)
> @@ -8,11 +8,12 @@
>
> ##=
> =
> =----------------------------------------------------------------------
> ===##
> LEVEL = ..
>
> -PARALLEL_DIRS = vmkit vmjc
> +PARALLEL_DIRS = vmkit
>
> include $(LEVEL)/Makefile.config
>
> ifeq ($(WITH_JNJVM), 1)
> + PARALLEL_DIRS += vmjc
> PARALLEL_DIRS += jnjvm
> endif
>
> Bye,
> Deano
> _______________________________________________
> LLVM Developers m...
2004 Oct 23
1
[LLVMdev] UPDATE: Makefile.rules Changes (IMPORTANT)
...list of subdirectories to be built. Fake targets are set up
> -# so that each of the targets "all", "install", and "clean" each build
> -# the subdirectories before the local target. DIRS are guaranteed to be
> -# built in order.
> -#
> -# 3. PARALLEL_DIRS - A list of subdirectories to be built, but that may be
> -# built in any order. All DIRS are built in order before PARALLEL_DIRS are
> -# built, which are then built in any order.
> -#
> -# 4. Source - If specified, this sets the source code filenames. If this
> -# is no...
2010 Sep 06
1
[LLVMdev] RFC: change build order (or location) of LLVMHello plugin
Good evening, Michael.
2010/9/5 Michael Spencer <bigcheesegs at gmail.com>:
> Do you know what the exact problem is? It would be best to fix the
> Makefile instead of moving it. And sense it is a transformation, the
> build system is broken if you _have_ to move it.
I am sorry, I don't understand what *the exact problem" is.
I can describe facts;
- Hello is the only
2007 Sep 10
2
[LLVMdev] profiling with llvm-gcc4?
How can I do function profiling and BB profiling with current llvm and
llvm-gcc4?
runtime/libprofile is disabled when using llvm-gcc4, but... is there any
alternative to linking with libprofile_rt.so?
How can I use llvm-prof? is utils/profile.pl obsolete?
Thanks in advance,
josem
2007 Sep 10
0
[LLVMdev] profiling with llvm-gcc4?
On Mon, 10 Sep 2007, Jose M. Moya wrote:
> How can I do function profiling and BB profiling with current llvm and
> llvm-gcc4?
>
> runtime/libprofile is disabled when using llvm-gcc4, but... is there any
> alternative to linking with libprofile_rt.so?
>
> How can I use llvm-prof? is utils/profile.pl obsolete?
The profiling support in LLVM hasn't been used for quite a
2007 Sep 11
1
[LLVMdev] profiling with llvm-gcc4?
...ems working again with this simple patch:
Index: runtime/Makefile
===================================================================
--- runtime/Makefile (revision 41794)
+++ runtime/Makefile (working copy)
@@ -11,11 +11,7 @@
include $(LEVEL)/Makefile.config
ifeq ($(LLVMGCC_MAJVERS),4)
-PARALLEL_DIRS :=
-install all::
- $(Echo) "Warning: These runtime libraries only need to be built
with"
- $(Echo) "Warning: llvm-gcc version 3. They are automatically
included"
- $(Echo) "Warning: with llvm-gcc version 4 and beyond"
+PARALLEL_DIRS := libprofile...
2009 Jan 19
3
[LLVMdev] building clang when present
...y require some changes to ‘Makefile.rules’ to work as
>>> intended, though. If there's interest in such a change, I can
>>> prepare
>>> a patch?
>>
>> Are OPTIONAL_DIRS parallel? For some reason, I was assuming not.
>
> Well, from my recollection, PARALLEL_DIRS and the other *_DIRS don't
> interact terribly well with each other with the current LLVM build
> system. It may or may not actually be executed parallel with other
> directories, but I wouldn't consider that a problem, as Clang itself
> contains quite a lot of source files, li...
2013 Oct 03
3
[LLVMdev] A way to write new pass by keeping source and build directories separate
...o /llvm-src and build it into /llvm-build
directories.
1. Write a new pass and Makefile as mentioned in LLVM doc 'Writing a new
pass'. Assume it is created in /llvm-src/lib/Transforms/NewPass directory.
2. Modify the Makefile in /llvm-src/lib/Transforms directory by adding
NewPass under PARALLEL_DIRS.
3. *make* in /llvm-build directory.
4. Thats it. If things go fine, newpass.so will be created in
/llvm-build/Debug+Asserts/lib directory.
5. The new pass can be loaded by modifying the command mentioned in the
LLVM doc (for Writing a new pass) as
opt -load /llvm-build/Debug+Asserts/lib/n...
2009 Jan 19
2
[LLVMdev] building clang when present
On Jan 19, 2009, at 11:55 AM, Dan Villiom Podlaski Christiansen wrote:
> In my humble opinion, using OPTIONAL_DIRS would be better and cleaner.
> It may require some changes to ‘Makefile.rules’ to work as
> intended, though. If there's interest in such a change, I can prepare
> a patch?
Are OPTIONAL_DIRS parallel? For some reason, I was assuming not.
2009 Jan 19
0
[LLVMdev] building clang when present
...r and
>> cleaner.
>> It may require some changes to ‘Makefile.rules’ to work as
>> intended, though. If there's interest in such a change, I can prepare
>> a patch?
>
> Are OPTIONAL_DIRS parallel? For some reason, I was assuming not.
Well, from my recollection, PARALLEL_DIRS and the other *_DIRS don't
interact terribly well with each other with the current LLVM build
system. It may or may not actually be executed parallel with other
directories, but I wouldn't consider that a problem, as Clang itself
contains quite a lot of source files, libraries and...
2009 Sep 03
0
[LLVMdev] LLVM 2.6 Cygwin Release
Tanya,
This patch at the end of this message is needed for Cygwin and GCC 4.2.x
series.
I also had to disable 'runtime/libprofile' by including the following in
'runtime/makefile' :-
ifeq ($(OS), Cygwin)
PARALLEL_DIRS := $(filter-out libprofile, $(PARALLEL_DIRS))
endif
There maybe a better fix to make it work.
Aaron
---------- Forwarded message ----------
From: Nick Lewycky <nicholas at mxc.ca>
Date: 2009/8/29
Subject: [llvm-commits] [llvm-gcc-4.2] r80424 -
/llvm-gcc-4.2/trunk/gcc/llvm-convert.cp...
2013 Jun 11
2
[LLVMdev] how to opt -load on cygwin
...I'm trying to load and run a pass on Cygwin target:
opt -load=mypass.dll -mypass
There is an LLVM example - Hello, however lib/Transforms/Makefile says
# No support for plugins on windows targets
and then excludes Hello from build
ifeq ($(HOST_OS), $(filter $(HOST_OS), Cygwin MingW Minix))
PARALLEL_DIRS := $(filter-out Hello, $(PARALLEL_DIRS))
endif
On the other hand, I found old suggestions to use
configure --enable-shared --disable-embed-stdcxx
and then link a pass to LLVM dynamic library, using the following Makefile
for the pass:
...
LOADABLE_MODULE=1
include $(LEVEL)/Makefile.common
LIBS+...
2006 May 10
2
[LLVMdev] llvm-gcc4 & mingw32
Hello, Everyone.
This is just brief description on building llvm-gcc4 with mingw32.
It's definitely non error-free and contains many "hacks", which should
be eliminated in the future.
1. Prerequisites
We're building in the folowing configuration:
1.1 GCC 3.4.5:
gcc -v
Reading specs from f:/research/mingw/bin/../lib/gcc/mingw32/3.4.5/specs
Configured with:
2005 May 19
3
[LLVMdev] [Cygwin] llvm 'make install' build errors
Reid,
I think it is the first time it is run that the errors occcur !?
Not sure but that would seem logical.
Aaron
2010 Oct 21
2
[LLVMdev] statically linked passes
...so far in the build system:
Within lib/Transforms/MyPass I have:
Makefile:
LEVEL = ../../..
LIBRARYNAME = LLVMMyPass
BUILD_ARCHIVE = 1
include $(LEVEL)/Makefile.common
CMakeLists.txt
add_llvm_library(LLVMMyPass MyPass.cpp)
And within the Transforms directory I added my directory to the list
of PARALLEL_DIRS within the Makefile there.
In the root llvm directory's CMakeLists.txt I added a call to
add_subdirectory(lib/Transforms/MyPass)
And I added create functions to LinkAllPasses.h.
Now when I build visual studio projects with cmake I have to manually
set up dependencies in the generated projec...
2013 Oct 04
0
[LLVMdev] A way to write new pass by keeping source and build directories separate
...c and build it into /llvm-build
directories.
> 1. Write a new pass and Makefile as mentioned in LLVM doc 'Writing a
new pass'. Assume it is created in /llvm-src/lib/Transforms/NewPass
directory.
> 2. Modify the Makefile in /llvm-src/lib/Transforms directory by adding
NewPass under PARALLEL_DIRS.
> 3. make in /llvm-build directory.
> 4. Thats it. If things go fine, newpass.so will be created in
/llvm-build/Debug+Asserts/lib directory.
> 5. The new pass can be loaded by modifying the command mentioned in the
LLVM doc (for Writing a new pass) as
>
>
> opt -load /llvm...
2006 Sep 02
2
[LLVMdev] Adding register allocator to LLVM
On 9/2/06, Chris Lattner <sabre at nondot.org> wrote:
>
> Make sure to add it to Codegen/LinkAllCodegenComponents.h.
I'm sure I did. I did so from the first time and I also needed to add my
library .a file to the USEDLIBS variable within llc makefile to build llc.
I wonder how lli links with all the rest LLVM as it seems to include no lib
within its makefile. May be I need to
2006 Sep 02
0
[LLVMdev] Adding register allocator to LLVM
On Sat, 2 Sep 2006, Anton Vayvod wrote:
> I'm sure I did. I did so from the first time and I also needed to add my
> library .a file to the USEDLIBS variable within llc makefile to build llc.
> I wonder how lli links with all the rest LLVM as it seems to include no lib
> within its makefile. May be I need to include/link my lib somewhere else?
Ah, that's probably it. Try