similar to: [LLVMdev] (possible) bytecode format change

Domagoj, > Is that change absolutely necessary? Unfortunately, yes. We're having at least two PRs opened for aliases including libstdc++ compilation in shared mode for x86/linux. > I've just spent 2 days compiling benchmarks. So, now I'd need to > ditch all that and start from scratch... No. Bytecode will be breaking only if it have module-wide assembler. I don't think

On Wed, Jan 21, 2004 at 08:25:23AM -0800, Robert Mykland wrote: > I'm the guy who is working on the LLVM bytecode documentation. The > document I have at present just supports the bytecodes my code > generator processes, though, which is far from all of them. As I get > farther along with my code generator I expect I'll get to the point > where everything kind of fits

---------- Forwarded message ---------- From: Anton Korobeynikov <anton at korobeynikov.info> Date: Wed, Dec 8, 2010 at 16:31 Subject: Re: [LLVMdev] wxGTK sample app compiled by llvm crashes on arm To: ankur jain <samyak3 at gmail.com> Hello, > I still have a query. Using llvm-gcc as cross-arm compiler will generate > bytecode specific to arm. > These bytecodes will work

Hello, Aaron. > /usr/src/llvm-gcc4/gcc/libgcc2.c: In function '__eprintf': > /usr/src/llvm-gcc4/gcc/libgcc2.c:1832: internal compiler error: > Segmentation fault > Please submit a full bug report, > with preprocessed source if appropriate. > See <URL:http://llvm.org/bugs> for instructions. You should: 1. Try to emit bytecode with --emit-llvm compiler switch. 1.1

Bill, > When I try to compile on Darwin now, I get this: Could you please provide LLVM bytecode, where bug is reproducible with llc? -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

I'm the guy who is working on the LLVM bytecode documentation. The document I have at present just supports the bytecodes my code generator processes, though, which is far from all of them. As I get farther along with my code generator I expect I'll get to the point where everything kind of fits together for me and I can finish it up. In the meantime, people are welcome to what I have

On May 24, 2006, at 5:03 AM, Anton Korobeynikov wrote: > Hello, Ashwin. > > You wrote Wednesday, May 24, 2006, 11:25:11 AM: > > AC> "Pass::getClassPassInfo<PassClass>() "Pass class not > AC> registered!"" failed: file > AC> "/cygdrive/c/llvm/llvm/include/llvm/PassAnalysisSupport.h", > line 76 > AC> Aborted > Same

Hi Anton, Is the patch going to be uploaded to the CVS source? Ashwin On 5/24/06, Evan Cheng <evan.cheng at apple.com> wrote: > > > On May 24, 2006, at 5:03 AM, Anton Korobeynikov wrote: > > > Hello, Ashwin. > > > > You wrote Wednesday, May 24, 2006, 11:25:11 AM: > > > > AC> "Pass::getClassPassInfo<PassClass>() "Pass class

All, Post 1.9 we will start using bytecode version 7. Version 6 corresponds to release 1.9. There is some work that needs to be done to make this happen but I'm too tired to think through it right now. I will address this first thing in the morning. In the meantime, the CVS head version of LLVM just changed what version 6 bytecodes means. That means your old version 6 bytecode (before the

Hi Thanks for the info, it led to the source of the error I was having. I was using llvm-gcc binaries (built with mingw I guess) to compile a .c file that is my language runtime, llvm-link'ing that with my frontend's .ll, and using an vcpp-built lli to run the resulting bytecode. This caused the special case in X86RegisterInfo::emitPrologue for "main" to try to align the stack

According to the instruction manual of this target machine, 'goto' should not be used in C code. :-/ Could you tell me a little more about your advice as to using 'reg2mem', if you're fine? Thank you so much, Anton. Best, Seung J. Lee ---- Original message ---- >Date: Sun, 15 Jul 2007 02:23:27 +0400 >From: Anton Korobeynikov <asl at math.spbu.ru> >Subject:

The patch is now in. Sorry about the delay! Evan On May 25, 2006, at 10:20 AM, Ashwin Chandra wrote: > Hi Anton, > Is the patch going to be uploaded to the CVS source? > > Ashwin > > > On 5/24/06, Evan Cheng <evan.cheng at apple.com> wrote: > > On May 24, 2006, at 5:03 AM, Anton Korobeynikov wrote: > > > Hello, Ashwin. > > > > You wrote

Hello, Philipp. > unsigned is 16 bit on my target platform. Could you please show LLVM bytecode? -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Hello, Ashwin. You wrote Wednesday, May 24, 2006, 11:25:11 AM: AC> "Pass::getClassPassInfo<PassClass>() "Pass class not AC> registered!"" failed: file AC> "/cygdrive/c/llvm/llvm/include/llvm/PassAnalysisSupport.h", line 76 AC> Aborted Same for me. AC> Wihtout the -march specified (using native x86 assembly) it does AC> convert it into

The alloca hook is in lib\System\Win32\DynamicLibrary.inc all the way at the bottom. You'll see a __MING32__ #ifdef around the definition. You just have to implement those methods and it'll work just fine. Jake On 6/24/07, Scott Graham <scott.llvm at h4ck3r.net> wrote: > > Hi > > Thanks for the info, it led to the source of the error I was having. > > I was using

Hi Evan, Actually the unrecognized commas disappeared with the patch. What remains is a call to ".local" which doesn't exist in x86 or at least is not compilable by g++. Ashwin On 5/25/06, Ashwin Chandra <ashwin.chandra1 at gmail.com> wrote: > > Hi Evan, > I updated cvs and recompilled llvm. Still getting some unrecognized commas > in the compilation of the

Hi Evan, I updated cvs and recompilled llvm. Still getting some unrecognized commas in the compilation of the assembly file after using llc. I guess this is still future work... Ashwin On 5/25/06, Evan Cheng <evan.cheng at apple.com> wrote: > > The patch is now in. Sorry about the delay! > > Evan > > On May 25, 2006, at 10:20 AM, Ashwin Chandra wrote: > > Hi

All, Just a heads up that the bytecode format changed again last night. If you have bc files, they need to be refreshed. If you're running a nightly tester, please refresh your llvm-gcc (mirror should be updated now, or soon). The change resulted from PR1146 which redesigns the parameter attribute feature. With the redesign it became possible to reduce the size of a function type definition

Dear All, Would somebody be able to update the Bytecode Format Manual with the 28 bit bytecode version numbers for LLVM 1.4, 1.5, and 1.6 (or point me to the file which defines it so I can look it up)? Thanks. -- John T. -- John T. Criswell Research Programmer University of Illinois at Urbana-Champaign "It's today!" said Piglet. "My favorite day," said Pooh.

On 9/5/07, Anton Korobeynikov <asl at math.spbu.ru> wrote: > Bill, > > > When I try to compile on Darwin now, I get this: > Could you please provide LLVM bytecode, where bug is reproducible with > llc? > Attached. Thanks! -bw -------------- next part -------------- A non-text attachment was scrubbed... Name: EH.bc Type: application/octet-stream Size: 872 bytes Desc: not