[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4ee8e077-feb4-c2ff-5eca-ef06012d34b3@virtuozzo.com>
Date: Fri, 6 Oct 2017 11:45:29 +0300
From: Andrey Ryabinin <aryabinin@...tuozzo.com>
To: Sodagudi Prasad <psodagud@...eaurora.org>,
nicolas.iooss_linux@....org, akpm@...ux-foundation.org,
mingo@...nel.org
Cc: linux-kernel@...r.kernel.org
Subject: Re: __ubsan_handle_type_mismatch converted to
__ubsan_handle_type_mismatch_v1
On 10/06/2017 05:29 AM, Sodagudi Prasad wrote:
> Hi All,
>
> Based on below links __ubsan_handle_type_mismatch has been renamed to __ubsan_handle_type_mismatch_v1.
>
> https://github.com/llvm-mirror/compiler-rt/commit/56faee71af1888ba12ab076b3d1f9bbe223493df#diff-21369cc6f3917b27df3ced8de89cf134
> https://www.mail-archive.com/gcc-bugs@gcc.gnu.org/msg535130.html
>
>
> When I tried to compile the kernel with LLVM seen following errors.
> arch/arm64/kernel/traps.o: In function `dump_backtrace':
> kernel/arch/arm64/kernel/traps.c:192: undefined reference to `__ubsan_handle_type_mismatch_v1'
> kernel/arch/arm64/kernel/traps.c:192: undefined reference to `__ubsan_handle_type_mismatch_v1'
> kernel/arch/arm64/kernel/traps.c:192: undefined reference to `__ubsan_handle_type_mismatch_v1'
> kernel/arch/arm64/kernel/traps.c:192: undefined reference to `__ubsan_handle_type_mismatch_v1'
> arch/arm64/kernel/traps.o: In function `dump_mem':
>
>
> Can I add __ubsan_handle_type_mismatch_v1 API similar to __ubsan_handle_type_mismatch()(I will send path for review)?
> If both apis are present, then there will be backward compatibility. Let me know if you have any other suggestions for this issue.
Sounds good, send the patch please.
>
> -Thanks, Prasad
>
Powered by blists - more mailing lists