Displaying 3 results from an estimated 3 matches for "getcpisymbol".
2019 Jul 12
2
Introducing an Alignment object in LLVM
...s have to be defensive to make sure assumptions hold (5)
- checking that an offset is aligned is sometimes done backward `Alignment
% Offset == 0` instead of `Offset % Alignment == 0` (6) (7)
- MachineConstantPoolEntry::Alignment encodes special information in its
topmost bit (8) but `AsmPrinter::GetCPISymbol` seems to use it directly (9)
instead of calling `getAlignment()` (10)
I have a patch to introduce alignment object in LLVM.
This patch does not fix the code but replaces the unsigned value by a type
so it's easier to introduce proper semantic later on.
The patch (11) is too big to be sent to...
2019 Jul 12
2
Introducing an Alignment object in LLVM
...ve to make sure assumptions hold (5)
> - checking that an offset is aligned is sometimes done backward
> `Alignment % Offset == 0` instead of `Offset % Alignment == 0` (6) (7)
> - MachineConstantPoolEntry::Alignment encodes special information in its
> topmost bit (8) but `AsmPrinter::GetCPISymbol` seems to use it directly (9)
> instead of calling `getAlignment()` (10)
>
> I have a patch to introduce alignment object in LLVM.
> This patch does not fix the code but replaces the unsigned value by a type
> so it's easier to introduce proper semantic later on.
>
> The pa...
2012 Apr 19
0
[LLVMdev] Target Dependent Hexagon Packetizer patch
...);
>> assert( (MO.getType() == MachineOperand::MO_ConstantPoolIndex)&&
>> - "Expecting constant pool index");
>> + "Expecting constant pool index");
>>
>> // Hexagon_TODO: Do we need name mangling?
>> O<< *GetCPISymbol(MO.getIndex());
>> diff --git a/lib/Target/Hexagon/HexagonInstrFormats.td b/lib/Target/Hexagon/HexagonInstrFormats.td
>> index c9f16fb..e3fa0ed 100644
>> --- a/lib/Target/Hexagon/HexagonInstrFormats.td
>> +++ b/lib/Target/Hexagon/HexagonInstrFormats.td
>> @@ -13,13 +13...