[llvm-dev] Problem with Aarch64 ?
Somenath Chakraborty via llvm-dev
llvm-dev at lists.llvm.org
Thu Sep 8 02:22:57 PDT 2016
Was there any specific reason to take the opposite path (from x86) ? - Just
curious to know.
On Thu, Sep 8, 2016 at 2:33 PM, Tim Northover <t.p.northover at gmail.com>
> On 7 September 2016 at 18:32, Somenath Chakraborty via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
> > The value to the formal argument is zero-extended, different from
> x86_64. Is
> > this a known issue ? Am I missing anything ?
> This is specified in the ABI document:
> Section 7.1 gives mappings from C types to underlying ones and says
> that "char" is actually an "unsigned byte". This applies to 32-bit
> AAPCS targets as well; but beware that Darwin targets don't follow
> AAPCS here, and char is signed again.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev