search for: bytecodeformat

Folks, I have completed a final draft of the bytecode documentation. You can find it in llvm/docs/BytecodeFormat.html in CVS. Or, if you'd prefer to view online, you can find it here: http://llvm.x10sys.com/llvm/docs/BytecodeFormat.html I'm soliciting your feedback on this document. Please let me know if anything is awkward or just plain wrong. Thanks, Reid. -------------- next part --------------...

I have only just begun looking through the docs for LLVM. I have read through some of the PP presentations to get an idea of the modularity of LLVM. May someone be so kind to point me to some documentation on how to communicate with the LLVM modules (specifically the optimizer) from some third party piece of software (my compiler)? I am hoping there is a file format, or some serialization, that

...tly deficient in this area as it didn't >correctly identify the type of lists used for the types and value >planes. The documentation has been updated to correctly reflect the >nature of the lists. > >Robert: if you could, please review: > >http://llvm.x10sys.com/llvm/docs/BytecodeFormat.html#symtab > >and let me know if it makes sense now. IMHO still not clear. The problem here is that too many things in this documentation are referred to as "slot number". I know that's how the comments read in the code, but it's unclear. The term is used both to des...

...k, function, and module. Basically, we want many extra fields to > be written out and read in. However, I cannot find a obvious way to do > this in current LLVM. Do you have any suggestion about this? We have a document describing the bytecode format here: [1] http://llvm.cs.uiuc.edu/docs/BytecodeFormat.html Also, a document on how to add new instructions, intrinsic functions: [2] http://llvm.cs.uiuc.edu/docs/ExtendingLLVM.html ([2] isn't exactly what you're asking for, but related) The question is, do you really want to have more extra fields in the instructions? What is it that you n...

...didn't >> correctly identify the type of lists used for the types and value >> planes. The documentation has been updated to correctly reflect the >> nature of the lists. >> >> Robert: if you could, please review: >> >> http://llvm.x10sys.com/llvm/docs/BytecodeFormat.html#symtab >> >> and let me know if it makes sense now. > > IMHO still not clear. The problem here is that too many things in this > documentation are referred to as "slot number". I know that's how the > comments read in the code, but it's unclear....

...le. Basically, we want many extra fields to >> be written out and read in. However, I cannot find a obvious way to do >> this in current LLVM. Do you have any suggestion about this? > > We have a document describing the bytecode format here: > [1] http://llvm.cs.uiuc.edu/docs/BytecodeFormat.html > Also, a document on how to add new instructions, intrinsic functions: > [2] http://llvm.cs.uiuc.edu/docs/ExtendingLLVM.html > ([2] isn't exactly what you're asking for, but related) > > The question is, do you really want to have more extra fields in the > instruct...

...cessary to make the ShiftInst become a BinaryOperator. This means the three shift instruction's opcodes had to be moved into the BinaryOps range and consequently all the opcodes after that got bumped up by three. This changes the bytecode format, unfortunately. The documentation (LangRef.html, BytecodeFormat.html) has been updated to reflect the changes. llvm-upgrade has been updated to perform the upgrade. Note, however, that it will insert a zext instruction (or constant expression) if the shifted value is not i8. In updating the test suite, this upgrade broke a few tests because the additional zext...

Dear Reid and Chris, I thought I should send this to the list in case anyone else is struggling to interpret bytecode files with the new docs. (1) First a bug I already mentioned to Reid. Unlike the other new module headers module 0x01 still uses the old 32-bit and 32-bit format instead of the new 5-bit and 27-bit format. Thus the first module in the file will be 0x00000001 followed by

...gt; you implemented it. Did you add another bytecode entry for the section > value mapping? Is it possible to add attributes to other elements like > functions as well? Yes, it was added to the .ll/.bc formats: http://llvm.cs.uiuc.edu/docs/LangRef.html#globalvars http://llvm.cs.uiuc.edu/docs/BytecodeFormat.html#globalinfo > Did you think about a mapping of common attributes on different > platforms. For instance DLLMain Entry point under Win32 and the > __attribute__((constructor)) under Linux. __attribute__((constructor)) is handled with a the llvm.globalctors global variable (even with...

...1.2. New Cool Features: 8. Reid finished up the LLVM bytecode analyzer tool, useful for inspecting bytecode file internals: http://llvm.cs.uiuc.edu/docs/CommandGuide/html/llvm-bcanalyzer.html 9. Reid completed the LLVM Bytecode Format Specification: http://llvm.cs.uiuc.edu/docs/BytecodeFormat.html 10. LLVM now has a very simple (though quite effective) implementation of a context-sensitive mod/ref analysis for global variables. For details, see http://llvm.cs.uiuc.edu/docs/AliasAnalysis.html#globalsmodref LLVM Core Additions: 11. The BinaryOperator class now has a BinaryOpera...

...a finished making all the documentation conform strictly to the HTML4.01 standard. 8. The LLVM Alias Analysis document is updated and vastly improved: http://llvm.cs.uiuc.edu/docs/AliasAnalysis.html 9. Reid started documenting the LLVM bytecode format: http://llvm.cs.uiuc.edu/docs/BytecodeFormat.html 10. The LLVM code generator interfaces and implementations are finally getting high-level documentation: http://llvm.cs.uiuc.edu/docs/CodeGenerator.html 11. Brian is converting all of the CommandGuide documents to perl pod files, so that we will eventually have man pages for all...

hi Chris! thanks for your reply. First of all I did not know about the history with the Annotation stuff. Annotable for me was a way how one could realize this things. So as I see it right now - it is more that Annotable will completly vanish soon. This is interesting to me. Chris Lattner schrieb: > On Fri, 24 Feb 2006, Jakob Praher wrote: > >> When translating a complex c