Displaying 3 results from an estimated 3 matches for "sext_loads".
Did you mean:
sext_load
2009 Feb 18
0
[LLVMdev] Possible error in LegalizeDAG
On Wed, Feb 18, 2009 at 10:14 AM, Villmow, Micah <Micah.Villmow at amd.com> wrote:
> I'm still trying to track down some alignment issues with loads(i.e. 8/16
> bit loads being turned into 32bit sign extending loads) and I cannot for the
> life of me seem to figure out how to enter this section of code:
>
> // If this is an unaligned load and the target doesn't support
2009 Feb 19
2
[LLVMdev] Possible error in LegalizeDAG
...I must support
i8 loads, however the hardware only supports natively 32bit aligned
loads, therefore I have to read in 4 i8's and unpack them and shift them
based on the read address. So any i8 load has a 75% chance of being
unaligned on my hardware, so I need a way to tell LLVM not to generate
sext_loads, or if it does to expand them. Everything that has been
suggested so far has not worked.
> Any hints would be greatly appreciated, this is a blocking issue that
I just
> cannot seem to resolve without modifying the LLVM codebase to remove
the
> extend + load -> extload combining step....
2009 Feb 18
2
[LLVMdev] Possible error in LegalizeDAG
I'm still trying to track down some alignment issues with loads(i.e.
8/16 bit loads being turned into 32bit sign extending loads) and I
cannot for the life of me seem to figure out how to enter this section
of code:
// If this is an unaligned load and the target doesn't support it,
// expand it.
if (!TLI.allowsUnalignedMemoryAccesses()) {
unsigned