Displaying 5 results from an estimated 5 matches for "constants_block".
2013 Jan 09
0
[LLVMdev] Global variable initializer type does not match global variable type
...op6=108 op7=97 op8=115 op9=115/>
<STRUCT_NAMED abbrevid=8 op0=0 op1=0 op2=6/>
<POINTER abbrevid=4 op0=7 op1=0/>
- <STRUCT_ANON abbrevid=6 op0=0 op1=0 op2=6/>
</TYPE_BLOCK_ID>
<GLOBALVAR abbrevid=4 op0=8 op1=0 op2=2 op3=0 op4=0 op5=0/>
<CONSTANTS_BLOCK NumWords=5 BlockCodeSize=4>
- <SETTYPE abbrevid=4 op0=9/>
+ <SETTYPE abbrevid=4 op0=7/>
<NULL/>
</CONSTANTS_BLOCK>
... all the same ...
So it pretty much seems that instantiating a constant struct with a
type which
is structurally identical to an exist...
2013 Jan 09
2
[LLVMdev] Global variable initializer type does not match global variable type
Hello.
I've managed to create a bitcode file (attached; also available at [1])
which produces
a series of identical errors when verified:
| Global variable initializer type does not match global variable type!
| %i.NilClass* @nil
When ran through llvm-dis and recompiled, through, it verifies
successfully. If I
disassemble it one more time, the result is identical to the first
2010 May 20
1
[LLVMdev] [PATCH] More BitCodeFormat.html improvements
The enclosed patch adds documentation for the PARAMATTR_BLOCK, TYPE_BLOCK,
and TYPE_SYMTAB_BLOCK records in the LLVM IR bitcode format.
I have started documenting CONSTANTS_BLOCK and FUNCTION_BLOCK and will send
patches when they are complete.
-Peter-
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100520/39b61edf/attachment.html>
-------------- next part --------------
A non...
2012 Sep 26
0
[LLVMdev] [PATCH / PROPOSAL] bitcode encoding that is ~15% smaller for large bitcode files...
...;
> diff --git a/include/llvm/Bitcode/LLVMBitCodes.h b/include/llvm/Bitcode/LLVMBitCodes.h
> index c1dc190..6c81739 100644
> --- a/include/llvm/Bitcode/LLVMBitCodes.h
> +++ b/include/llvm/Bitcode/LLVMBitCodes.h
> @@ -33,9 +33,9 @@ namespace bitc {
> UNUSED_ID1,
>
> CONSTANTS_BLOCK_ID,
> - FUNCTION_BLOCK_ID,
> + FUNCTION_BLOCK_ID, // Deprecated in favor of FUNCTION_BLOCK_ID_REL
FUNCTION_BLOCK_ID_REL -> FUNCTION_BLOCK_REL_ID
Is there any point in having this on a per-function basis, why not have it be
per-module?
>
> - UNUSED_ID2,
> + FUNCTION...
2012 Sep 26
9
[LLVMdev] [PATCH / PROPOSAL] bitcode encoding that is ~15% smaller for large bitcode files...
Hi all,
I've been looking into how to make llvm bitcode files smaller. There is
one simple change that appears to shrink linked bitcode files by about 15%.
See this spreadsheet for some rough data:
https://docs.google.com/spreadsheet/ccc?key=0AjRrJHQc4_bddEtJdjdIek5fMDdIdFFIZldZXzdWa0E
The change is in how operand ids are encoded in bitcode files. Rather than
use an "absolute