-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FP16 使用armv7推理有问题 #9639
Comments
您好,我们已经收到了您的问题,会安排技术人员尽快解答您的问题,请耐心等待。请您再次检查是否提供了清晰的问题描述、复现代码、环境&版本、报错信息等。同时,您也可以通过查看官网文档、常见问题、历史Issue来寻求解答。祝您生活愉快~ Hi! We've received your issue and please be patient to get responded. We will arrange technicians to answer your questions as soon as possible. Please make sure that you have posted enough message to demo your request. You may also check out the API,FAQ and Github Issue to get the answer.Have a nice day! |
armv7的板子不支持fp16指令,armv8.2架构以后的板子才支持,你可以是用picodet的fp32模型在armv7的板子上推理 |
请问意思是我现在用的CPU不支持arm v7下使用FP16吗?还是所有的CPU都不支持arn v7下使用FP16? |
你这个展锐是:由两颗1.8 GHz的Arm Cortex-A75 CPU 和六颗1.8 GHz的Arm Cortex-A55 处理器组成的吗?如果是A75、A55是支持v7 跑fp16的,Log信息看不出什么问题,建议用c++ shell demo只跑模型,export GLOG_v=6把log打开 |
由两颗1.8 GHz的Arm Cortex-A75 CPU 和六颗1.8 GHz的Arm Cortex-A55 处理器组成的吗? -- 是的 |
@mjp9527 请问你说的 "如果是A75、A55是支持v7 跑fp16的" 中的fp16库是哪个分支哪个节点编译出来的?能告知一下吗?因为目前我用某个commit 编fp16 32位时,编译都会报错,编 64位就没问题。 |
标题:使用paddle lite在arm v7上进行FP16模型预测出问题
版本、预测库信息:
预测信息
复现信息:使用的是pciodet的fp16模型推理
问题描述:当设置为armv8时,使用paddlelite推理没问题,但是切换到armv7,则出现如下错误
com.baidu.paddle.lite.demo.ssd_detection
PID: 7980
UID: 10220
Flags: 0x30e8bf46
Package: com.baidu.paddle.lite.demo.ssd_detection v1 (1.0)
Foreground: Yes
Process-Runtime: 265639
Build: EEBBK/sm6150/sm6150:11/RKQ1.201112.002/V1.2.0_210910:userdebug/release-keys
Build fingerprint: 'EEBBK/sm6150/sm6150:11/RKQ1.201112.002/V1.2.0_210910:userdebug/release-keys'
Revision: '0'
ABI: 'arm'
Timestamp: 2022-11-04 14:26:48+0800
pid: 7980, tid: 8019, name: GLThread 140 >>> com.baidu.paddle.lite.demo.ssd_detection <<<
uid: 10220
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
Abort message: 'stack corruption detected (-fstack-protector)'
r0 00000000 r1 00001f53 r2 00000006 r3 c07592d0
r4 c07592e4 r5 c07592c8 r6 00001f2c r7 0000016b
r8 c07592d0 r9 c07592e0 r10 c0759300 r11 c07592f0
ip 00001f53 sp c07592a0 lr f09bfeed pc f09bff00
backtrace:
#00 pc 00038f00 /apex/com.android.runtime/lib/bionic/libc.so (abort+172) (BuildId: 3f6c9092328e50137ce743f77ee900af)
Crash #1 pc 00046d97 /apex/com.android.runtime/lib/bionic/libc.so (__stack_chk_fail+10) (BuildId: 3f6c9092328e50137ce743f77ee900af)
squeeze net performance on ios #2 pc 000efcbb /data/app/~~6uSBqnn8Nji7fAlyhSLVAg==/com.baidu.paddle.lite.demo.ssd_detection-EeiETBPRkzc1zDTXhM6RUQ==/lib/arm/libpaddle_light_api_shared.so (BuildId: e9e54eed9d2c622e77473b044568662f43c2467c)
The text was updated successfully, but these errors were encountered: