[llvm-dev] Problem with Aarch64 ? (original) (raw)
Somenath Chakraborty via llvm-dev llvm-dev at lists.llvm.org
Thu Sep 8 02:22:57 PDT 2016
- Previous message: [llvm-dev] Problem with Aarch64 ?
- Next message: [llvm-dev] Problem with Aarch64 ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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> wrote:
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 x8664. Is > this a known issue ? Am I missing anything ?
This is specified in the ABI document: http://infocenter.arm.com/help/topic/com.arm.doc. ihi0055b/IHI0055Baapcs64.pdf. 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. Tim. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160908/1cd2fb71/attachment.html>
- Previous message: [llvm-dev] Problem with Aarch64 ?
- Next message: [llvm-dev] Problem with Aarch64 ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]