Displaying 2 results from an estimated 2 matches for "load192".
Did you mean:
load12
2016 Nov 11
2
Is the correct behavior of getelementptr i192* for opt + llc -march=aarch64?
On 10 November 2016 at 04:29, MITSUNARI Shigeo via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
>>Is your default target aarch64? Otherwise opt may be assuming a different
>>target which might explain the difference.
>
> No, My target is x86-64, x86, arm, aarch64, ..., then I'll avoid using i192* and datalayout.
I believe Tom's point was about the line:
% opt-3.8
2016 Nov 09
10
Is the correct behavior of getelementptr i192* for opt + llc -march=aarch64?
Hi all,
opt and opt + llc generate the difference aarch64 asm code for the following LLVM code.
Is it intended behavior?
I expected (A) because I cast %p from i192* to i64*.
The information is dropped by opt and 8-byte padding is inserted or I write a bad code?
% cat a.ll
define void @store0_to_p4(i192* %p)
{
%p1 = bitcast i192* %p to i64*
%p2 = getelementptr i64, i64* %p1, i64 3
%p3 =