Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] Problem building LLVM in cygwin environment."
2007 Mar 09
2
[LLVMdev] compile errors with demo projects Stacker and Hello
Hi all!
I have sucessfully installed LLVM 1.9 under FreeBSD on a x86 PC.
I have successfully executed "An Example Using the LLVM Tool Chain" that is
written in the document http://llvm.org/docs/GettingStarted.html
When I tried out the demo projects "Hello" and "Stacker" I get compile errors. When I run "gmake" in the directory
2007 Mar 09
0
[LLVMdev] compile errors with demo projects Stacker and Hello
If I remember correctly, you get the following warning when you
configure LLVM:
configure:2087: WARNING: Unknown project (Stacker) won't be configured
automatically
That leads would lead me to believe that you need to run configure
inside llvm/projects/Stacker (and inside llvm/projects/Hello) before you
run gmake inside of them. I don't know for sure, but perhaps that might
fix
2007 Mar 29
0
[LLVMdev] compile error with HowToUseJIT
Hi all!
I have installed LLVM 1.9 under FreeBSD and read the documentation.
Problem: examples/HowToUseJIT fails to compile.
I entered the following command in the directory /usr/home/x/llvm1.9/examples/HowToUseJIT :
gmake ENABLE_OPTIMIZED=0
It stops after producing object files (.o) without comment.
When I enter the following (from the documentation):
g++ `llvm-config --ldflags` -o HowToUseJIT
2009 Jan 19
2
[LLVMdev] cygwin build patch
LLVM doesn't build out of the box on Cygwin, because Cygwin defines
uint32_t as "unsigned long" rather than "unsigned int".
The attached patch allows me to build head of svn (rev 62510) on
Cygwin using GCC 4. Can this be committed please?
I realise that the DataTypes.h.in part might be controversial. Also,
there's probably a better place to put it, but I'm not
2009 Jan 19
0
[LLVMdev] cygwin build patch
On Jan 19, 2009, at 7:44 AM, Jay Foad wrote:
> LLVM doesn't build out of the box on Cygwin, because Cygwin defines
> uint32_t as "unsigned long" rather than "unsigned int".
>
> The attached patch allows me to build head of svn (rev 62510) on
> Cygwin using GCC 4. Can this be committed please?
Thanks applied:
2011 May 26
1
JGR/Deducer Installation
Hi,
Sorry if this is to wrong mailing list. In that case, please point me
to correct mailing list.
Please also excuse rather long mail - I am not sure what piece of
information would be useful for anybody who could help me.
Couple of days back I had put a query about box-plots using GUI. I
got some excellent suggestions. One of them was to use JGR/Deducer.
It worked quite well for my needs.
2008 Feb 21
0
[LLVMdev] Removing inlining of library functions
The defined gcc interface for this is -fno-builtin. It seems not be
to be working in llvm-gcc, however.
On Feb 20, 2008, at 6:55 PM, Cristina Cifuentes wrote:
> I am interested in analyzing the bytecode code produced for C files.
> By default, inlining of user and library functions (libc) is done. If
> I turn off inlining (-disable-inlining in gccas and gccld) then no
> inlining
2009 Jun 24
2
Limit of Glusterfs help
HI:
Was there a limit of servers which was used as storage in Gluster ?
2009-06-24
eagleeyes
???? gluster-users-request
????? 2009-06-24 03:00:42
???? gluster-users
???
??? Gluster-users Digest, Vol 14, Issue 34
Send Gluster-users mailing list submissions to
gluster-users at gluster.org
To subscribe or unsubscribe via the World Wide Web, visit
2008 Feb 21
6
[LLVMdev] Removing inlining of library functions
I am interested in analyzing the bytecode code produced for C files.
By default, inlining of user and library functions (libc) is done. If
I turn off inlining (-disable-inlining in gccas and gccld) then no
inlining is done. I want to be able to inline user code but disallow
library code to be inlined.
In trying to understand the InlineSimple.cpp code, I see that library
functions are
2014 Mar 20
2
[LLVMdev] load bytecode from string for jiting problem
Hello Willy,
Here is the dump from one of my bitcode files:
0000000 42 43 c0 de 21 0c 00 00 25 05 00 00 0b 82 20 00
As expected, 0x42 (= B), 0x43 (= C), xc0 and 0xde are in correct order. In
your case, the first byte is read as 37 (= 0x25). I wonder why? When you
check the bytes yourself, you get expected results. When the same bytes are
read from Stream object, you get a different result (maybe
2009 Feb 24
1
building asterisk-1.6.0.6 failed!
Hi!
I have problems building asterisk 1.6.0.6.
./configure --prefix=/usr
make
gets me:
enerating embedded module rules ...
[CC] extconf.c -> extconf.o
In file included from /usr/local/include/datatypes.h:50,
from /usr/local/include/err.h:49,
from extconf.c:45:
/usr/local/include/integers.h:50:67: error: srtp_config.h: No such file
or directory
In file
2008 Feb 22
2
[LLVMdev] Removing inlining of library functions
On Thu, 21 Feb 2008, Dale Johannesen wrote:
> The defined gcc interface for this is -fno-builtin. It seems not be
> to be working in llvm-gcc, however.
Please file a reduced testcase in bugzilla,
-Chris
>
>> I am interested in analyzing the bytecode code produced for C files.
>> By default, inlining of user and library functions (libc) is done. If
>> I turn off
2014 Mar 20
2
[LLVMdev] load bytecode from string for jiting problem
This segfault occuring only under valgrind,
in shell way, and in gdb way i have
Invalid bitcode signature
simple_scev_dynamic_array: /home/willy/apollo/llvm/include/llvm/Support/ErrorOr.h:258: storage_type *llvm::ErrorOr<llvm::Module *>::getStorage() [T = llvm::Module *]: Assertion `!HasError && "Cannot get value when an error exists!"' failed.
Command terminated by
2009 Jun 24
0
Gluster-users Digest, Vol 14, Issue 34
HI:
Was there a limit of servers which was used as storage in Gluster ?
2009-06-24
eagleeyes
???? gluster-users-request
????? 2009-06-24 03:00:42
???? gluster-users
???
??? Gluster-users Digest, Vol 14, Issue 34
Send Gluster-users mailing list submissions to
gluster-users at gluster.org
To subscribe or unsubscribe via the World Wide Web, visit
2008 Feb 22
0
[LLVMdev] Removing inlining of library functions
On Feb 21, 2008, at 5:38 PM, Chris Lattner wrote:
> On Thu, 21 Feb 2008, Dale Johannesen wrote:
>> The defined gcc interface for this is -fno-builtin. It seems not be
>> to be working in llvm-gcc, however.
>
> Please file a reduced testcase in bugzilla,
>
> -Chris
Er, well, now that I've looked at the correct output files, it is
actually working.
>>> I
2006 Dec 14
3
[LLVMdev] ThisCall / Compilation problems
Hi all,
A few things.
Firstly, I've got a working implementation of the X86ThisCall calling
convention, but I'm unsure how to go about submitting it.
(I'm not really sure how to go about creating patch files etc, but would
like to contribute to the project).
Also, I'm using MS Visual C++ Express, and there are a few things that stop
llvm1.9 (and the current CVS release) from
2009 Jan 20
4
[LLVMdev] cygwin build patch
>> I realise that the DataTypes.h.in part might be controversial. Also,
>> there's probably a better place to put it, but I'm not sure where.
>
> I didn't apply this part. What problems does it cause to not have
> this? Can we fix uses of max and min?
I get these errors in lib:
.../lib/Analysis/ValueTracking.cpp:162: error: no matching function
for call to
2010 Sep 06
1
[LLVMdev] DataTypes.h Header File
Hi
This is a beginner's question. I’m trying to compile Kaleidoscope Ch3
example under MinGW. As I understand most errors result from header file
DataTypes.h be missing.
I was unable to find DataTypes.h header file in llvm/System folder. Instead,
the folder contain DataTypes.h.in and DataTypes.h.cmake files. Shall I use
them to create DataTypes.h header file? Any help would be much
2009 May 12
1
[LLVMdev] MSVC cstdint
In the llvm file include/llvm/Support/DataTypes.h (.in/.cmake), for
MSVCit defines some macros that are defined in the cstdint.hpp file in
boost (and boost does it better, detailed below):
The basic error is:
R:\SDKs\boost\built_head\include\boost-1_38\boost/cstdint.hpp(347) :
warning C4005: 'INT8_C' : macro redefinition
2004 Sep 27
0
[LLVMdev] Hardcoded HAVE_* defines in the DataTypes.h include file
Henrik Bach wrote:
> Hi
>
> I noticed that these defines (line 35 to 37) are hardcoded in the
> DataTypes.h include file:
> ----------------
> #define HAVE_SYS_TYPES_H 1
> #define HAVE_INTTYPES_H 1
> #define HAVE_STDINT_H 1
> ----------------
>
> Shouldn't they have be defined by the configure script into
> llvm/Config/config.h?
These lines are set by