Displaying 3 results from an estimated 3 matches for "abialignment".
2009 Feb 18
2
[LLVMdev] Possible error in LegalizeDAG
...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 ABIAlignment = TLI.getTargetData()->
getABITypeAlignment(LD->getMemoryVT().getTypeForMVT());
if (LD->getAlignment() < ABIAlignment){
Result =
ExpandUnalignedLoad(cast<LoadSDNode>(Result.getNode()), DAG,...
2017 May 22
2
How exactly is datatype alignment determined?
The 8 in the data layout string should have been converted to a byte value
by this code before it was passed to setAlignment. As far as I cant ell
getAlignment should return the byte alignment that was passed to
setAlignment, not the bit alignment from the string.
// ABI alignment.
if (Rest.empty())
report_fatal_error(
"Missing alignment specification in
2017 May 22
2
How exactly is datatype alignment determined?
On Mon, 22 May 2017, Dr. ERDI Gergo wrote:
> Actually, tracking down the sequence of function calls, it turns out that '8'
> is ultimately coming from the following call in DataLayout::getAlignment:
>
> getAlignmentInfo(AGGREGATE_ALIGN, 0, abi_or_pref, Ty);
>
> this seems to return 8 with the following datalayout string:
>
>