Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] compilaton problem"
2007 Dec 23
1
[LLVMdev] compilaton problem
Hi.
For weeks now I have problems compiling llvm from svn, compilation ends with
llvm[2]: Compiling Lexer.cpp for Release build
/home/borist/builds/llvm/lib/AsmParser/Lexer.l: In function 'int
llvmAsmlex()':
/home/borist/builds/llvm/lib/AsmParser/Lexer.l:278: error: 'PURE' was
not declared in this scope
/home/borist/builds/llvm/lib/AsmParser/Lexer.l:279: error: 'CONST'
2008 Mar 24
1
[LLVMdev] AsmParser/Lexer.l error
Hello
With the latest LLVM from Subversion (rev48737 from
http://llvm.org/svn/llvm-project/llvm/trunk) I'm getting
make[2]: Entering directory `/usr/src/Lang/llvm/_Obj/lib/AsmParser'
llvm[2]: Flexing Lexer.l
llvm[2]: Compiling Lexer.cpp for Debug build
/usr/src/Lang/llvm/lib/AsmParser/Lexer.l: In function 'int llvmAsmlex()':
/usr/src/Lang/llvm/lib/AsmParser/Lexer.l:278: error:
2010 Jun 21
2
[LLVMdev] MC: Object file specific parsing
Hi Daniel,
attached is a patch that pushes most of the object file specific parsing
out of AsmParser and down into MachOAsmParser. This was done as a
cleanup for the ELF work. I know that you're not happy with this
approach, particularly the fact that as we add more object file formats
and assembler dialects, it's going to cause a class explosion. But I was
hoping that we could use this
2006 Jan 11
1
[LLVMdev] Re: [llvm-commits] CVS: llvm/lib/AsmParser/Lexer.cpp Lexer.l
For VC++, I solved this by having bison/flex put the files into the obj
directories. I also have it unconditionally regenerate the files if
bison/flex is available, and copy them from src if they are not.
Chris Lattner wrote:
> On Wed, 11 Jan 2006, Vladimir A. Merzliakov wrote:
>
>> I can't build LLVM CFE after this patchs
>>
2006 Jan 11
1
[LLVMdev] Re: [llvm-commits] CVS: llvm/lib/AsmParser/Lexer.cpp Lexer.l
No solutions come to mind. Conflicts are conflicts and must be resolved
manually. This situation should only occur if you change the .l/.y file
and then update the .h/.cpp files after someone else has changed
the .l/.y file and regenerated the .h and .cpp. That doesn't seem like a
high frequency scenario that we need to worry about. Not sure there's
much we could do even if it was.
Reid.
2006 Jan 11
0
[LLVMdev] Re: [llvm-commits] CVS: llvm/lib/AsmParser/Lexer.cpp Lexer.l
On Wed, 11 Jan 2006, Vladimir A. Merzliakov wrote:
> I can't build LLVM CFE after this patchs
> http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060109/030639.html
> http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060109/030654.html
This is most likely because you have conflict markers in the generated
files in the lib/AsmParser directory. Try removing
2006 Jan 11
4
[LLVMdev] Re: [llvm-commits] CVS: llvm/lib/AsmParser/Lexer.cpp Lexer.l
I can't build LLVM CFE after this patchs
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060109/030639.html
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060109/030654.html
Build terminated with messages:
--8X----------------------------------------------
llvm[2]: Compiling Lexer.cpp for Debug build
In file included from
2012 May 18
3
[LLVMdev] Adding a New Instruction to LLVM IR
Hello;
I was planning to add a new instruction to the LLVM IR (and later to MIPS
backend) for TLS(Thread level speculation) support. For this I tried to
follow the steps described in http://llvm.org/docs/ExtendingLLVM dot
html#instruction.
But I could not find any llvm/lib/AsmParser/Lexer.l
and llvm/lib/AsmParser/llvmAsmParser.y file in both the svn repository and
the source code downloaded
2009 Jun 28
0
[LLVMdev] The document fault in llvm doc. And a comiling error
most html document need to add
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
int <head> section of html
such as
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
other staff
</head>
this is the correct style.
.\llvm\docs\SourceLevelDebugging.html
Chris Lattner sabre at nondot.org
2011 Nov 09
2
[LLVMdev] [cfe-dev] LLVM 3.0rc3 Testing Beginning
On 7 November 2011 22:00, Bill Wendling <wendling at apple.com> wrote:
> We are starting on our third (and hopefully last) round of testing for LLVM 3.0. Please visit:
>
> http://llvm.org/pre-releases/3.0/rc3/
>
> for the sources. There are also binaries for Darwin up there, with
> more to come during the week. Please build this release candidate,
> test it out
2012 May 20
1
[LLVMdev] Error While Inserting New Instruction to LLVM IR
Hello;
I wanted to insert two new terminator instructions in LLVM IR. I modified
the necessary files (as mentioned in the tutorial in LLVM site and some
more to meet the new structure of LLVM, (e.g no Lexer.l now, we have
LLLexer.cpp. Again in the tutorial, files like LLVMBitCodes.h,
include/llvm-c/core.h that need to be modified are not mentioned) But I am
getting the error while building
2015 Feb 02
2
[LLVMdev] Inconsistencies or intended behaviour of LLVM IR?
On Mon, Feb 2, 2015 at 9:51 AM, Robin Eklind <carl.eklind at myport.ac.uk>
wrote:
> (forgot to cc the list)
>
> Answers, questions and assumptions are inlined in the response.
>
> If someone with knowledge of the LLVM IR type system could take a look at
> my assumptions below I'd be very happy.
>
> On 01/30/2015 02:24 AM, Sean Silva wrote:
>
>> On Thu,
2013 Nov 27
0
[LLVMdev] Bug in Language Reference? %0 versus %1 as starting index.
(gah, this turned into a huge digression, sorry)
The implicit numbering of BB's seems to be a pretty frequent issue for
people. Surprisingly, the issue boils down to simply changing the IR asm
(.ll file) syntax so that it can have "unnamed BB's" in a recognizable way
that fits in with how unnamed values work (the asmprinter makes an effort
to print a comment with the BB number,
2015 Jan 13
3
[LLVMdev] [RFC] First-class debug info IR: MDLocation (redux)
After splitting `Metadata` apart from `Value`, I'm finally back to the
first step [1] of representing debug info more directly in IR [2]:
`MDLocation`.
[1]: http://lists.cs.uiuc.edu/pipermail/llvmdev/2014-October/078173.html
"First-class debug info IR: MDLocation"
[2]: http://lists.cs.uiuc.edu/pipermail/llvmdev/2014-October/077715.html
"Less memory and greater
2004 Jul 21
0
[LLVMdev] GC questions.
On Wed, 21 Jul 2004, Chris Lattner wrote:
>
> Yes, this makes a tremendous amount of sense. Do you think you could
> prepare some patches to make this happen? If you have any questions, feel
> free to ask :)
Ok, a patch[1] is attached. I didn't care to coerce the offset, since I
assume that it is an uint, but maybe I should? Hopefully I've understood
the llvm source
2013 Nov 27
0
[LLVMdev] Bug in Language Reference? %0 versus %1 as starting index.
On Tue, Nov 26, 2013 at 9:58 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote:
> Thanks for the lecture :) But I was not planning on changing a single
> line in LLVM/Clang. I stick to the documentation until I've learned to
> swim, perhaps even forever. Ah, now I see. You thought I meant "should I
> modify the code to do this or that." I only meant to change
2013 Nov 27
2
[LLVMdev] Bug in Language Reference? %0 versus %1 as starting index.
Thanks for the lecture :) But I was not planning on changing a single line
in LLVM/Clang. I stick to the documentation until I've learned to swim,
perhaps even forever. Ah, now I see. You thought I meant "should I modify
the code to do this or that." I only meant to change the documentation.
Please refer to the patch I've sent on LLVM-commits. That's about what I
had
2009 Jan 08
1
[LLVMdev] Build failure on x86_64
Hello!
I see the following build failure of the sources at the top of the trunk, on
x86_64.
make[2]: Entering directory `<llvm-root>/build/llvm/lib/AsmParser'
llvm[2]: Compiling LLLexer.cpp for Release build
llvm[2]: Compiling LLParser.cpp for Release build
<llvm-root>/src/llvm/lib/AsmParser/LLParser.cpp: In member function 'bool
llvm::LLParser::ParseGlobal(const
2010 Nov 09
1
[LLVMdev] uninitialized value warnings: LLVMParser.cpp
These warnings started appearing recently when building LLVM:
llvm[2]: Compiling LLParser.cpp for Release build
/Volumes/Data/Users/kremenek/llvm/lib/AsmParser/LLParser.cpp: In member function ‘bool llvm::LLParser::ParseBr(llvm::Instruction*&, llvm::LLParser::PerFunctionState&)’:
/Volumes/Data/Users/kremenek/llvm/lib/AsmParser/LLParser.cpp:3195: warning: ‘Op1’ may be used uninitialized in
2008 Mar 09
2
[LLVMdev] linker error (llvm-config, eclipse)
Hi,
I'm playing around with llvm and the Kaleidoscope tutorial and first of
all I have to say I'm really impressed. LLVM rocks!
Unfortunately I've now run into a linker error while trying to optimize
the IR or turn it to bitcode and likely due to my very limited
experience with c++ I just can't figure out how to resolve it.
The linker complains that the llvm::WriteBitcodeToFile