01-19-2018 03:35 PM
Hi ,
This is Richard from SystemView inc.
When i build HLS in windows 10, it comes
C:/Xilinx/Vivado/2017.4/win64/tools/clang/bin\..\lib\clang\3.1/../../../include/c++/4.5.2\exception_ptr.h:132:13: error: unknown type name 'type_info' const type_info*
C:/Xilinx/Vivado/2017.4/win64/tools/clang/bin\..\lib\clang\3.1/../../../include/c++/4.5.2\nested_exception.h:62:5: error: the parameter for this explicitly-defaulted copy constructor is const, but a member or base requires it to be non-const nested_exception(const nested_exception&) = default;
the same code has no problem in Linux environment.
01-19-2018 08:08 PM
@richard12345 Can you post the actual code you are trying to compile? Perhaps just the offending part...
What version of HLS you're running on Windows? And on Linux?
01-21-2018 09:04 PM
01-22-2018 11:38 AM - edited 01-22-2018 11:55 AM
01-22-2018 12:01 PM
Hi Balkrishan,
I am using Windows 10 Professional Creators Update (64-bit), English.
There are some log info as attachment, could you help to look at it.
There are some one who face the same issue, https://github.com/jingpu/Halide-HLS/issues/5
i follow his instruction, modify the file of
C:/Xilinx/Vivado/2017.4/win64/tools/clang/bin\..\lib\clang\3.1/../../../include/c++/4.5.2\exception_ptr.h:134:13
and
C:/Xilinx/Vivado/2017.4/win64/tools/clang/bin\..\lib\clang\3.1/../../../include/c++/4.5.2\nested_exception.h:62:5
But i do not want to touch Vivado files, so i want to check whether there are other solutions without touch vivado files.
Best regards
Richard
Best regards
Richard
01-22-2018 12:22 PM - edited 01-22-2018 01:28 PM
@richard12345 This is not a normal HLS project. It has a custom makefile. It points to files external to the project that are not included.
Can you create a new HLS project with a snippet of code that does not compile?
I cannot help much in the present case.
01-22-2018 04:47 PM
05-17-2019 07:31 AM
Hi,
The workaround I found for Vivado 2018.3 on Windows 10 is to manually edit some Vivado files.
#ifndef _EXCEPTION_PTR_H #define _EXCEPTION_PTR_H #ifdef __clang__ class type_info; #endif [...]
// __throw_with_nested(_Ex&&, const nested_exception* = 0) // original __throw_with_nested(_Ex&&, const nested_exception*) // modified
I don't know if this is breaking anything else in particular, but it seems to work flawlessly now.
Best,
Stefano