similar to: [LLVMdev] Extra command line options from the LLVM CommandLine parser

Hello LLVM list, I'm working on a wrapper for LibC and I think it would work a whole lot better for what I'm trying to do if I wasn't forced to use a specific endianness. I'm trying to make it work in such a way that the compiler can generate code for a generic LLVM target such that the bitcodes won't need to have the alignment information or endianness until the final link

Hello Anton, Our main.bc was generated with the following command line: llvm-g++ -Illvm\include -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -c -emit-llvm -omain.bc main.cpp The amos.bc file was generated by our experimental llvm-peg parser generator whose internal workings are assembled internally using LLVM Assembly. The parser generator links a C++ library bitcode with C bindings called

Hello > It is complaining about not being able to find __gxx_personality_sj0 and the LLVM command line parser-related files.  What else do we need to link? This is personality function for sjlj eh. How the source bitcode files in questions were generated? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Hello again, My partner and I am modifying a PEG parser generator to produce LLVM bitcode from a version of a parsing expression grammar that takes LLVM Assembly as code. It accepts external libraries in its current state so we are writing an external library in C++ using C bindings for the linkage. Trying to get it to link is proving to be more challenging than expected. My partner is trying

Hello Anton, We used the release tarball. Oh! I forgot to mention it's the version 2.5 stable release that we've been developing with. Thanks, --Sam ----- Original Message ---- > From: Anton Korobeynikov <anton at korobeynikov.info> > To: Samuel Crow <samuraileumas at yahoo.com> > Cc: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > Sent: Fri,

Hello Anton, While we have been discussing this, my partner discovered the source of where the sj/lj stuff is coming from. Does this mean that the LLVM libraries we're using are broken? Type.cpp ..\..\..\..\llvm\lib/libLLVMCore.a(Type.cpp.obj):Type.cpp.text+0x722): undefined reference to `__gxx_personality_sj0' ..\..\..\..\llvm\lib/libLLVMCore.a(Type.cpp.obj):Type.cpp.text+0x750):

Hello, Samuel > llvm-g++ -Illvm\include -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -c -emit-llvm -omain.bc main.cpp Ok. How was llvm-g++ built? Have you used release tarball, or built everything by hands? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Hello, Samuel > While we have been discussing this, my partner discovered the source of where the sj/lj stuff is coming from.  Does this mean that the LLVM libraries we're using are broken? > > Type.cpp > ..\..\..\..\llvm\lib/libLLVMCore.a(Type.cpp.obj):Type.cpp.text+0x722): undefined reference to `__gxx_personality_sj0' >

----- Original Message ---- > From: Óscar Fuentes <ofv at wanadoo.es> > To: Samuel Crow <samuraileumas at yahoo.com> > Cc: Óscar Fuentes <ofv at wanadoo.es>; LLVM Developers Mailing List ><llvmdev at cs.uiuc.edu> > Sent: Fri, January 14, 2011 4:39:57 PM > Subject: Re: Circular Deps from CMake build using makefile > > Samuel Crow <samuraileumas

Hi, It looks like the "Writing a custom parser" example from the CommandLine 2.0 Library Manual is broke for 3.0+. This used to work with llvm-2.9. When I try to compile it I get: ../include/llvm/Support/CommandLine.h:964:20: error: no viable conversion from 'const FileSizeParser' to 'parser<unsigned>' I fixed it by changing struct FileSizeParser : public

https://llvm.org/docs/CommandLine.html#writing-a-custom-parser describes how to implement a custom parser, but they're all marked `final`, so I can't inherit. Is there a reason for this? If not, I'll submit patch with tests. thanks... don -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello Óscar, This time the autotools version of LLVM trunk build with Clang trunk compiled in Debug+Asserts mode without complaint with --enable-bindings=none. I suspect this makes something fishy looking with the CMake build. Do you need logfiles from configure? Thanks again, --Sam ----- Original Message ---- > From: Óscar Fuentes <ofv at wanadoo.es> > To: Samuel Crow

After waiting through about 2 hours of hard drive spinning for Clang to link under my Xubuntu Lucid Lynx Linux setup on VirtualBox, ld finally just gave up trying to link it. I was using CMake's build scripts on version 2.7 release of LLVM and Clang. The version of ld is (GNU Binutils for Ubuntu) 2.20.1-system.20100303. Can anyone confirm this problem? If needed I'll cross-post this to

Hello Óscar, The single-threaded build failed the same place as the double threaded build failed which is the same place I just indicated in my previous post. The ../llvm/configure script version failed with OCaml building with about 600 assembler errors since I built it in AMD64 mode. (Oops.) Should I disable OCaml from the configure script and try again? Assembler error, input left in

Samuel Crow <samuraileumas at yahoo.com> writes: > This time the autotools version of LLVM trunk build with Clang trunk compiled in > Debug+Asserts mode without complaint with --enable-bindings=none. I suspect > this makes something fishy looking with the CMake build. Do you need logfiles > from configure? I'm clueless about what's happening there. The cyclic

Samuel Crow <samuraileumas at yahoo.com> writes: > I have attached the logfiles here. I think you didn't set CMAKE_BUILD_TYPE while configuring the cmake build. On your build directory, please do: make clean cmake -DCMAKE_BUILD_TYPE=Debug path/to/your/llvm/source/root make If that doesn't work, show the exact command lines you used for invoking cmake and the

Hi David: I'd actually like to use a custom parser in a tool I'm developing, parsing YAML files. The partial fix for my purposes was: --- a/llvm/include/llvm/Support/CommandLine.h +++ b/llvm/include/llvm/Support/CommandLine.h @@ -1044,7 +1044,7 @@ extern template class basic_parser<float>; //-------------------------------------------------- // parser<std::string> //

Hi Chris, I was thinking that CreateValueName() was the way to add a symbol to a symbol table. Perhaps I'm thinking about this wrong. Here's what I've got: I've got a string generated by the parser which is constant. I need to add it to the symbol table so that, on starting the second pass of my compiler, I can dump all of the string constants to be generated as code. I

I don't think I quite understand this... suppose for example you're trying to use an LLVM-based toolchain running on an x86 PC to write code for a device that uses an ARM processor in big endian mode, so you tell the LLVM code generator "generate code for ARM, big endian"... are you saying the optimizer will actually assume the target device is little endian because the

Hi, I've developed editor prototype for TableGen files (td). It is Eclipse plugin based on IMP project (The IDE Meta-Tooling Platform). Editor has outline, folding, coloring, go to definition, etc. As any prototype, editor has some limitations (e.g. no cross-file indexing). If there is any interest to such tool I will improve it a bit and then publish. Also considering llvm asm (ll) editing