similar to: [LLVMdev] error in /lib/CodeGen/MachOWriter.cpp: line 200

I'll look at these. First scan looks good. Are you able to run some tests? Evan On Feb 28, 2009, at 9:36 AM, Aaron Gray wrote: > I have done a possible cleanup patch for the MachineCodeEmitter, > ELFWriter, and MachOWriter classes. It removes the two > startGVStub(), and finishGVStub() JIT specific methods. > > You may remember the following comments :- > >

I have done a possible cleanup patch for the MachineCodeEmitter, ELFWriter, and MachOWriter classes. It removes the two startGVStub(), and finishGVStub() JIT specific methods. You may remember the following comments :- /// JIT SPECIFIC FUNCTIONS - DO NOT IMPLEMENT THESE HERE! To get rid of these easily turned out to be a semicomplex modification because of the JITInfo classes dependance on

Hello Chris Sat, 2 Sep 2006 11:34:55 -0700 (PDT) you wrote: > Intresting, I guess your gcc is treating uint32_t as different from > unsigned. I applied the patch you suggested, thanks! Mingw build is ok here (it uses 3.4.4 version), so, difference is definitely in runtime library. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State

On 2 May 2010 19:32, Nathan Jeffords <blunted2night at gmail.com> wrote: > Thanks for both of your feedback, I will attempt to make it fit LLVM coding > standards better before I resubmit my work. You can send me early drafts to run past GCC, send me something that works. As far as the hooks I put in, they are really only there so I could build > the object exporter outside of

Hi all! I didn't manage to link my regalloc to lli (I added USEDLIBS to its makefile). Without it I can't run tests cause they need lli to be built. So how can I link createMyRegisterAllocator function to lli? Thanks. On 8/22/06, Anton Vayvod <avayvod at gmail.com> wrote: > > I managed to link my RegAlloc.a library to llc tool but can;t make the > same with lli tool.

Hi all, I have interest in some ideas, some I've seen in the Open project pages (copied straight from there) and some are by my own, they are: 1) Implement MachOWriter and ELFWriter to allow LLVM-based compilers to bypass an external assembler. This may include the idea of an assembler for inline assembly 2) Write a disassembler for machine code that would use TableGen to output

The current CVS version doesn't compile on Linux: MachOWriter.h:583: error: 'strlcpy' was not declared in this scope Rafael

Aaron, I mailed in the same mail twice (by mistake), you answered both copies. Differently! In any case, I've re-read what exists. I'm dumping what I understand here, so that we can discuss in detail. I'm using MachO as the example object format, as the ELF code is totally broken and outdated. Lets use the following as the basis for our discussion? There are 3 classes which

Owen Anderson wrote: > There's nothing particularly stopping you from having your > installation package include copies of gas and ld, I disagree. gas and ld are not available on Windoze, except via MinGW. Yes I can make or tell my customers to install MinGW, but if MinGW is installed, then I don't need LLVM. (More about this further ahead) > You're welcome to think

> Aaah. Wasn't quite sure what you were doing here. I'm not positive > what llvm can emit via the writers (there's support for all parts of > the file format), but it could be extended to write one out. I'm just > not quite sure why :) > > -eric Well, ultimately I'm curious about what it would take to port a JVM based language (http://openquark.org) to

>> Sorry, I disagree actually the MachineCodeEmitter or the >> 'MachineCodeWritter' does not do any file handling at all. Do look at the >> code for the MachineCodeWritter and you will see it only writes to memory >> and if it reaches the end of the allotted memory I believe higher ordered >> logic reallocates a larget buffer and starts again from scratch.

Thanks for both of your feedback, I will attempt to make it fit LLVM coding standards better before I resubmit my work. As far as the hooks I put in, they are really only there so I could build the object exporter outside of LLVM, I think having it built directly in like others is preferable in the end. I do think it would be useful if projects had the option of extending supported formats

On 2 May 2010 10:53, Anton Korobeynikov <anton at korobeynikov.info> wrote: > Hello, Nathan > I'll let others comment on MC hooks, I just made a very brief look > over the contents of the archive. You can find the comments below. > Yes I looked at this and there are several ways but TargetAsmBackend looked the bast place to deal with the MCStreamer choice for different

Hi Nick, On 8/28/2013 6:37 PM, Nick Kledzik wrote > $cat 1.c > int _start() { return 0; } > $gcc -c 1.c > $ld -u myundef 1.o > ==> Does not throw any error, the resolver was hinted that myundef was a undefined weak symbol. > Wow. Reading the gnu ld man page, that is not obvious. How can you make a non-weak undefined on the command line? That is, how can you force and error

On Sun, May 2, 2010 at 1:47 PM, Aaron Gray <aaronngray.lists at googlemail.com>wrote: > On 2 May 2010 19:32, Nathan Jeffords <blunted2night at gmail.com> wrote: > >> Thanks for both of your feedback, I will attempt to make it fit LLVM >> coding standards better before I resubmit my work. > > > You can send me early drafts to run past GCC, send me something

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

I managed to link my RegAlloc.a library to llc tool but can;t make the same with lli tool. Should I use USEDLIBS variable in lli makefile (like llc) or there is another way? On 8/20/06, Fernando Magno Quintao Pereira <fernando at cs.ucla.edu> wrote: > > > Dear Anton, > > you can add your register allocator strait iin the > "lib/CodeGen/Passes.cpp", and then

install configuration built successfully too. llvm-gcc version is: gcc version 4.0.1 LLVM <Apple Computer, Inc. build 5400> how can I test it? I need to run make check in llvm/obj dir or in llvm-gcc/obj dir? Thanks On 8/4/06, Anton Vayvod <avayvod at gmail.com> wrote: > > Yes, I didn't install it myself. > > llvm-gcc4 has built successfully. > > Making

Dear Anton, you can add your register allocator strait iin the "lib/CodeGen/Passes.cpp", and then 're-make' it: "makellvm llc", on the top of lib/CodeGen. It is faster than running make from LLVMOBJDIR. The problem is that it only add to llc the changes on the lib/CodeGen directory. If you change other parts, a make from LLVMOBJDIR will synchronize it. Try adding

On Oct 23, 2007, at 05:52, BGB wrote: > I am assuming then that some external assembler is used (such as > 'gas')?... In the static compilers, yes. The JIT directly serializes instructions into memory without the aid of an external assembler. There are also experimental built-in assemblers; LLVM calls them object writers[1]. > it looks like much of the interconnection