[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <56E276C7-8204-48DD-B5C5-BF5B1452248A@arm.com>
Date: Sun, 7 Sep 2014 08:30:24 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: Mark Charlebois <charlebm@...il.com>
Cc: Arnd Bergmann <arnd@...db.de>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Behan Webster <behanw@...verseincode.com>,
Will Deacon <Will.Deacon@....com>,
"zhichang.yuan@...aro.org" <zhichang.yuan@...aro.org>,
"dsaxena@...aro.org" <dsaxena@...aro.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] arm64: LLVMLinux: Provide __aeabi_* symbols which are needed for clang
On 7 Sep 2014, at 03:30, Mark Charlebois <charlebm@...il.com> wrote:
> On Sat, Sep 6, 2014 at 7:16 AM, Arnd Bergmann <arnd@...db.de> wrote:
>>
>> On Friday 05 September 2014 16:23:14 behanw@...verseincode.com wrote:
>>> + * 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.
>
> http://infocenter.arm.com/help/topic/com.arm.doc.ihi0043d/IHI0043D_rtabi.pdf
>
> See section 4.3.4 Memory copying, clearing, and setting
What does this document have to do with arm64 (AArch64, A64)? We don’t
need such symbols on arm64. Also, the arm64 kernel links with libgcc (no
immediate need AFAICT but the compiler does not guarantee the intrinsics
would always be generated inline).
Catalin--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists