[llvm-bugs] [Bug 42556] New: Clang backend error when using vmax_f16 neon intrinsic
via llvm-bugs
llvm-bugs at lists.llvm.org
Tue Jul 9 10:50:55 PDT 2019
https://bugs.llvm.org/show_bug.cgi?id=42556
Bug ID: 42556
Summary: Clang backend error when using vmax_f16 neon intrinsic
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: ARM
Assignee: unassignedbugs at nondot.org
Reporter: pirama at google.com
CC: kristof.beyls at arm.com, llvm-bugs at lists.llvm.org,
peter.smith at linaro.org, sjoerd.meijer at arm.com,
srhines at google.com, Ties.Stuij at arm.com
See the attached link: https://godbolt.org/z/vTp2yV
Source:
$ cat fp16.c
#include <arm_neon.h>
float16x4_t m(float16x4_t a, float16x4_t b) {
return vmax_f16(a, b);
}
Fail: clang -c -O2 -target armv7-linux-eabi -march=armv8.2-a+fp16 -mfpu=neon
Pass: clang -c -O2 -target armv7-linux-eabi -march=armv8.2-a+fp16
-mfpu=neon-fp-armv8
The error message is below:
fatal error: error in backend: Do not know how to split the result of this
operator!
clang-9: error: clang frontend command failed with exit code 70 (use -v to see
invocation)
I think the frontend and backend are inconsistent when dealing with this
intrinsic.
Adding Sjoerd Meijer who has recent changes related to this for comments.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20190709/7c946cca/attachment.html>
More information about the llvm-bugs
mailing list