cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
yhy.xilinx
Adventurer
Adventurer
434 Views
Registered: ‎06-20-2019

Vitis error during emulation run

Hello,

I am trying to run an application on the VITIS platform. I chose Hardware for the build configuration at first. My application hung while running on the card. I wanted to debug and wanted to run the application in Emulation-SW configuration. Yet, I am getting errors. Why would I get such an error as following?

 

ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/floatn.h:87:‘__float128’ does not name a type; did you mean ‘__cfloat128’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdlib.h:152:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdlib.h:245:‘_Float128’ has not been declared
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdlib.h:330:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/wchar.h:406:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/wchar.h:523:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdint.h:43:‘__int_least8_t’ does not name a type; did you mean ‘__intptr_t’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdint.h:44:‘__int_least16_t’ does not name a type; did you mean ‘__int16_t’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdint.h:45:‘__int_least32_t’ does not name a type; did you mean ‘__int32_t’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdint.h:46:‘__int_least64_t’ does not name a type; did you mean ‘__int64_t’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdint.h:49:‘__uint_least8_t’ does not name a type; did you mean ‘__uintmax_t’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdint.h:50:‘__uint_least16_t’ does not name a type; did you mean ‘__uint16_t’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdint.h:51:‘__uint_least32_t’ does not name a type; did you mean ‘__uint32_t’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdint.h:52:‘__uint_least64_t’ does not name a type; did you mean ‘__uint64_t’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/cstdint:58:‘::int_least8_t’ has not been declared
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/cstdint:59:‘::int_least16_t’ has not been declared
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/cstdint:60:‘::int_least32_t’ has not been declared
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/cstdint:61:‘::int_least64_t’ has not been declared
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/cstdint:76:‘::uint_least8_t’ has not been declared
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/cstdint:77:‘::uint_least16_t’ has not been declared
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/cstdint:78:‘::uint_least32_t’ has not been declared
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/cstdint:79:‘::uint_least64_t’ has not been declared
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:511:‘uint_least16_t’ does not name a type; did you mean ‘uint_fast16_t’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:584:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:587:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:592:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:592:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:595:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:599:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:608:‘uint_least32_t’ does not name a type; did you mean ‘uint_fast32_t’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:681:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:684:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:689:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:689:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:692:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /media/yahya/HDD/setups/VITIS/kurulum/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:696:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls-helper-functions.h:21:‘_Float128’ was not declared in this scope
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls-helper-functions.h:25:‘_Float128’ was not declared in this scope
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls-helper-functions.h:30:‘_Float128’ was not declared in this scope
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls-helper-functions.h:33:‘_Float128’ was not declared in this scope
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls-helper-functions.h:36:‘_Float128’ was not declared in this scope
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls-helper-functions.h:39:‘_Float128’ was not declared in this scope
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls-helper-functions.h:39:‘_Float128’ was not declared in this scope
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls-helper-functions.h:39:expression list treated as compound expression in initializer [-fpermissive]
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls-helper-functions.h:42:‘_Float128’ was not declared in this scope
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:53:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:53:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:55:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:55:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:57:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:57:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:59:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:59:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:62:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:62:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:64:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:64:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:66:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:66:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:71:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:71:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:73:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:73:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:75:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:75:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:80:variable or field ‘sincosf128’ declared void
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:80:‘_Float128’ was not declared in this scope
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:80:‘_Float128’ was not declared in this scope
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:79:‘__sinx’ was not declared in this scope
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:80:‘_Float128’ was not declared in this scope
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:79:‘__cosx’ was not declared in this scope
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:80:variable or field ‘__sincosf128’ declared void
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:80:‘_Float128’ was not declared in this scope
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:80:‘_Float128’ was not declared in this scope
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:79:‘__sinx’ was not declared in this scope
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:80:‘_Float128’ was not declared in this scope
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:79:‘__cosx’ was not declared in this scope
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:85:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:85:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:87:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:87:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:89:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:89:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:95:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:95:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:98:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:98:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:101:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:101:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:104:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:104:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:107:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:107:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:110:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:110:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:114:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:114:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:119:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:119:‘_Float128’ does not name a type; did you mean ‘_Float32x’?
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:122:‘_Float128’ does not name a type; did you mean ‘_Float32x’?

I am not getting this while running on Hardware configuration.

 

Thank you for your valuable time.

Tags (3)
0 Replies