Displaying 3 results from an estimated 3 matches for "zpti2grw".
2012 Oct 12
2
[LLVMdev] Target backend not converting char* to struct properly.
...which is perfectly fine. However, it also keeps the 1-alignment
of the char array, which is not ok, as then the assignment (store) to the
'an_int_field' gets converted into a 4-byte aligned store instruction -
which of course fails when run.
My test case can be seen at http://pastebin.com/zPTi2GRW. Does anyone know
what I might need to do in my backend to make this work properly - perhaps
correct the definition of my 'store' instructions, or set a data-layout for
a struct type somewhere?
Thanks,
Stephen
-------------- next part --------------
An HTML attachment was scrubbed...
URL:...
2012 Oct 12
0
[LLVMdev] Target backend not converting char* to struct properly.
.... However, it also keeps the 1-alignment of
> the char array, which is not ok, as then the assignment (store) to the
> 'an_int_field' gets converted into a 4-byte aligned store instruction -
> which of course fails when run.
>
> My test case can be seen at http://pastebin.com/zPTi2GRW. Does anyone know
> what I might need to do in my backend to make this work properly - perhaps
> correct the definition of my 'store' instructions, or set a data-layout for
> a struct type somewhere?
Your code has undefined behavior; you're just getting lucky if it
works anywh...
2012 Oct 12
1
[LLVMdev] Target backend not converting char* to struct properly.
...gt; 1-alignment of
> > the char array, which is not ok, as then the assignment (store) to the
> > 'an_int_field' gets converted into a 4-byte aligned store instruction -
> > which of course fails when run.
> >
> > My test case can be seen at http://pastebin.com/zPTi2GRW. Does anyone
> know
> > what I might need to do in my backend to make this work properly -
> perhaps
> > correct the definition of my 'store' instructions, or set a data-layout
> for
> > a struct type somewhere?
>
> Your code has undefined behavior; you'...