Displaying 20 results from an estimated 7000 matches similar to: "[LLVMdev] Reader.cpp:464: error: `intptr_t' undeclared (first use this function)"
2011 Jan 31
0
[LLVMdev] llvm::Pass::Pass(llvm::PassKind, intptr_t): Assertion `pid && "pid cannot be 0"' failed.
llvm/include/llvm/Pass.h:93: llvm::Pass::Pass(llvm::PassKind,
intptr_t): Assertion `pid && "pid cannot be 0"' failed.
On Mon, Jan 31, 2011 at 3:55 PM, Surinder <surifilms at gmail.com> wrote:
> I have written a new pass, it compiles ok but crashes when i run it
> with error (llvm::Pass::Pass(llvm::PassKind, intptr_t): Assertion `pid
> && "pid
2011 Jan 31
2
[LLVMdev] llvm::Pass::Pass(llvm::PassKind, intptr_t): Assertion `pid && "pid cannot be 0"' failed.
I have written a new pass, it compiles ok but crashes when i run it
with error (llvm::Pass::Pass(llvm::PassKind, intptr_t): Assertion `pid
&& "pid cannot be 0"' failed.).
The pass is :
using namespace llvm;
namespace
{
struct Dfl : public FunctionPass {
static char ID;
Dfl() : FunctionPass(ID) { }
virtual bool runOnFunction(Function &F) {
bool
2004 Dec 21
0
[LLVMdev] win32 broken again
Jeff,
Thanks for reporting this. I had no idea ::read was being used in
ReaderWrappers. I have re-implemented it using istream facilities. This
should be much more portable. Please try again and let me know if its
better.
Thanks,
Reid.
On Mon, 2004-12-20 at 22:31, Jeff Cohen wrote:
> Primitive Unix I/O should not be used outside of lib/System:
>
>
2004 Dec 21
2
[LLVMdev] win32 broken again
Primitive Unix I/O should not be used outside of lib/System:
c:\llvm\lib\Bytecode\Reader\ReaderWrappers.cpp(140) : error C2039:
'read' : is not a member of 'operator``global namespace'''
2017 Mar 29
1
[PATCH] mllib: cast integer pointers to intptr_t as intermediate step
This make sure there is no mismatch between the size of the integer
value that Int64_val returns, and the size of the guestfs_h pointer.
This should fix the warning on 32bit environments (and thus build, when
--enable-werror is enabled).
---
mllib/visit-c.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mllib/visit-c.c b/mllib/visit-c.c
index b46dd33..b1c1216 100644
---
2004 Sep 19
1
[LLVMdev] Path.cpp patch to lib/System/Interix
Hi,
Just a minor fix to get Path.cpp to compile on Interix.
Henrik
_________________________________________________________________
Find det, du s�ger med MSN S�g http://search.msn.dk/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Path.cpp.zip
Type: application/x-zip-compressed
Size: 463 bytes
Desc: not available
URL:
2013 Jan 31
0
[LLVMdev] intptr_t support in llvm
Hi all,
I tried compiling an opencl kernel with intptr_t datatype. However it gives
error by default using LLVM/Clang 3.2 for nvptx . To allow usage, I tried
following typedefs ( by looking at tests in llvm sources ).
typedef int intptr_t;
and
typedef __typeof( (int*) 0) intptr_t;
Both definitions compiles the code, however gives following warning.
warning: incompatible pointer to integer
2004 Sep 15
2
[LLVMdev] HowToUseJIT.cpp - file: 'llvm/ADT/iterator': No such file or directory
Hi
I'm trying to compile HowToUseJIT.cpp, but it seems that iterator definition
is missing:
--------------------Configuration: HowToUseJIT - Win32
Debug--------------------
Compiling...
HowToUseJIT.cpp
c:\sfu\usr\local\src\llvm\include\llvm\adt\ilist(41) : fatal error C1083:
Cannot open include file: 'llvm/ADT/iterator': No such file or directory
Error executing cl.exe.
I've
2004 Dec 24
3
[LLVMdev] win32 broken again
Well... that didn't take long. I'm not sure what you did, Reid, with
Path.cpp, but it broke VC++:
Bytecode.lib(ReaderWrappers.obj) : error LNK2001: unresolved external
symbol "public: __thiscall llvm::sys::Path::Path(class
std::basic_string<char,struct std::char_traits<char>,class
std::allocator<char> > const &)"
(??0Path at sys@llvm@@QAE at
2015 May 07
2
[LLVMdev] Integer ID for LLVM::Instruction*?
David,
As you suggested, I try to compile the following test code:
*include "llvm/IR/Instruction.h"#include "stdint.h"extern void
callback(intptr_t);void foo(){ llvm::Instruction* i; intptr_t
zzzz=static_cast<intptr_t>(i); callback(zzzz);}*
but got this compilation error:
* 'intptr_t' (aka 'long') is not allowed intptr_t
2008 Oct 16
2
[LLVMdev] bug in the JIT global variable emitter
> + /// allocateSpace - reserves space in the current block if any, or
> + /// allocate a new one of the given size + virtual void
> *allocateSpace(intptr_t Size, unsigned Alignment); +
> Please capitalize "reserves".
ok.
> + /// allocateSpace - general-purpose space allocator
> Better comments please. :-) Also please end the sentence with a period
> or Chris'
2006 May 09
1
[LLVMdev] Memory leaks in LLVM
Hi,
Probably some of the leaks Valgrind reports are spurious, but the numbers
seem to be significant enough to demand some attention:
==10132== LEAK SUMMARY:
==10132== definitely lost: 15,624 bytes in 558 blocks.
==10132== indirectly lost: 44,548 bytes in 1,591 blocks.
==10132== possibly lost: 37,576 bytes in 98 blocks.
==10132== still reachable: 1,336,876 bytes in 1,364 blocks.
2008 Oct 16
0
[LLVMdev] bug in the JIT global variable emitter
On Oct 16, 2008, at 11:29 AM, Nuno Lopes wrote:
>> + /// allocateSpace - reserves space in the current block if any, or
>> + /// allocate a new one of the given size + virtual void
>> *allocateSpace(intptr_t Size, unsigned Alignment); +
>> Please capitalize "reserves".
>
> ok.
>
>
>> + /// allocateSpace - general-purpose space allocator
>>
2008 Oct 16
0
[LLVMdev] bug in the JIT global variable emitter
Thanks Nuno and Dale. Some comments:
+ /// allocateSpace - reserves space in the current block if any, or
+ /// allocate a new one of the given size + virtual void
*allocateSpace(intptr_t Size, unsigned Alignment); +
Please capitalize "reserves".
+ /// allocateSpace - general-purpose space allocator
Better comments please. :-) Also please end the sentence with a period
or Chris'
2010 Oct 01
2
trouble building 4.0.1
I finally decided to build 4.0.1 on my OpenSuSE box. I''ve been plodding along and resolving issues/dependencies as needed but now I''m stumped. While building I get the following message:
cc1: warnings being treated as errors
netfront.c:41:32: error: variably modified ‘tx_freelist’ at file scope
netfront.c:44:34: error: variably modified ‘rx_buffers’ at file scope
2019 Jan 15
2
Reducing the number of ptrtoint/inttoptrs that are generated by LLVM
> As with many things in the C and C++ specifications, this has very
> little relationship to real-world code. The biggest example I've seen
> that violates this rule is the way that the FreeBSD kernel implements
> per-CPU storage, but in a fairly ad-hoc analysis of existing C/C++ code
> we found quite a few cases where subtraction occurred between objects.
Hello David,
If C
2004 Dec 24
0
[LLVMdev] win32 broken again
Hi Jeff,
Typically, I've found out that these missing functions are placed beneath
lib/System/Unix in some of *.cpp files. These function can be copied to
their respectively lib/System/Win32 *.cpp files.
Henrik.
----Original Message Follows----
From: Jeff Cohen <jeffc at jolt-lang.org>
Reply-To: jeffc at jolt-lang.org, LLVM Developers Mailing List
<llvmdev at
2008 Feb 04
0
[LLVMdev] Exception handling in JIT
Looks sane. Thanks.
Evan
On Feb 1, 2008, at 1:24 AM, Nicolas Geoffray wrote:
> Dear all,
>
> Here's a new patch with Evan's comments (thx Evan!) and some cleanups.
> Now the (duplicated) exception handling code is in a new file:
> lib/ExecutionEngine/JIT/JITDwarfEmitter.
>
> This patch should work on linux/x86 and linux/ppc (tested).
>
> Nicolas
> Index:
2007 Dec 11
0
[LLVMdev] Exception handling in JIT
On Dec 10, 2007, at 9:52 AM, Nicolas Geoffray wrote:
> Hi everyone,
>
> Here's a patch that enables exception handling when jitting. I've
> copy/pasted _many_code from lib/Codegen/DwarfWriter.cpp, so we may
> need
> to factorize it, but the functionality is there and I'm very happy
> with
> it :)
Very nice! I don't know enough about EH, someone else
2009 Oct 08
2
[LLVMdev] question on code in PointerIntPair.h
around line 45 a bitmask is computed as:
PointerBitMask =
~(uintptr_t)(((intptr_t)1 << PtrTraits::NumLowBitsAvailable)-1),
my question is why is the shift performed on intptr_t? Wouldn't the
following be ok?
PointerBitMask =
~(((uintptr_t)1 << PtrTraits::NumLowBitsAvailable)-1),
Thanks in advance,
Maurizio