From: behanw@converseincode.com (Behan Webster)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: LLVMLinux: Provide __aeabi_* symbols which are needed for clang
Date: Sat, 06 Sep 2014 19:28:19 -0700 [thread overview]
Message-ID: <540BC2C3.1070509@converseincode.com> (raw)
In-Reply-To: <2954780.2t9bpyu7ov@wuerfel>
On 09/06/14 07:16, Arnd Bergmann wrote:
> On Friday 05 September 2014 16:23:14 behanw at converseincode.com wrote:
>> --- /dev/null
>> +++ b/arch/arm64/lib/eabi.c
>> @@ -0,0 +1,32 @@
>> +/*
>> + * linux/lib/eabi.c
> Please don't put the file names in the files themselves, it's redundant
> and in this case actually wrong.
Will fix.
>> + * Copyright (C) 2012 Mark Charlebois
>> + */
>> +
>> +/*
>> + * EABI routines
> Does EABI specify these function names? I would think that they are
> just random libgcc (whatever that is called in clang) functions.
These specialized functions are part of the ABI for the ARM architecture
(AEABI). They aren't random.
Memcpy and memmove *could* might be satisfied with linker magic instead.
But memset uses the reverse parameter list.
Behan
--
Behan Webster
behanw at converseincode.com
WARNING: multiple messages have this Message-ID (diff)
From: Behan Webster <behanw@converseincode.com>
To: Arnd Bergmann <arnd@arndb.de>, linux-arm-kernel@lists.infradead.org
Cc: catalin.marinas@arm.com, will.deacon@arm.com,
zhichang.yuan@linaro.org, Mark Charlebois <charlebm@gmail.com>,
dsaxena@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: LLVMLinux: Provide __aeabi_* symbols which are needed for clang
Date: Sat, 06 Sep 2014 19:28:19 -0700 [thread overview]
Message-ID: <540BC2C3.1070509@converseincode.com> (raw)
In-Reply-To: <2954780.2t9bpyu7ov@wuerfel>
On 09/06/14 07:16, Arnd Bergmann wrote:
> On Friday 05 September 2014 16:23:14 behanw@converseincode.com wrote:
>> --- /dev/null
>> +++ b/arch/arm64/lib/eabi.c
>> @@ -0,0 +1,32 @@
>> +/*
>> + * linux/lib/eabi.c
> Please don't put the file names in the files themselves, it's redundant
> and in this case actually wrong.
Will fix.
>> + * Copyright (C) 2012 Mark Charlebois
>> + */
>> +
>> +/*
>> + * EABI routines
> Does EABI specify these function names? I would think that they are
> just random libgcc (whatever that is called in clang) functions.
These specialized functions are part of the ABI for the ARM architecture
(AEABI). They aren't random.
Memcpy and memmove *could* might be satisfied with linker magic instead.
But memset uses the reverse parameter list.
Behan
--
Behan Webster
behanw@converseincode.com
next prev parent reply other threads:[~2014-09-07 2:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 23:23 [PATCH] arm64: LLVMLinux: Provide __aeabi_* symbols which are needed for clang behanw at converseincode.com
2014-09-05 23:23 ` behanw
2014-09-06 14:16 ` Arnd Bergmann
2014-09-06 14:16 ` Arnd Bergmann
2014-09-07 2:28 ` Behan Webster [this message]
2014-09-07 2:28 ` Behan Webster
2014-09-07 2:30 ` Mark Charlebois
2014-09-07 2:30 ` Mark Charlebois
2014-09-07 7:30 ` Catalin Marinas
2014-09-07 7:30 ` Catalin Marinas
2014-09-08 21:01 ` Mark Charlebois
2014-09-08 21:01 ` Mark Charlebois
2014-09-08 21:53 ` Behan Webster
2014-09-08 21:53 ` Behan Webster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=540BC2C3.1070509@converseincode.com \
--to=behanw@converseincode.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.