chhenning
chhenning
### MWE v1 for Test 2 ``` #define _CRT_SECURE_NO_WARNINGS #include #include using namespace boost::gil; void draw_line() { using ref_t = const bit_aligned_pixel_reference; using ptr_t = bit_aligned_pixel_iterator; using pixel_t = std::iterator_traits::value_type;...
### MWE v2 for Test 2 (`minimal_chhenning.cpp`) ``` #define _CRT_SECURE_NO_WARNINGS 1 #include #include using namespace boost::gil; int main() { using ref_t = const bit_aligned_pixel_reference; using ptr_t = bit_aligned_pixel_iterator; using pixel_t...
@mloskot Do you think this is a compiler bug only with VS2017 x64? Should we try VC2015 or VS2017 x32?
Can someone please provide a minimal reproducible code sample?
Great! Are you using any fancy compiler switches like the ones @stefanseefeld mentioned?
:-) This one I call fancy: `-fno-strict-aliasing`
@mloskot you are correct. What about the other bug?
@dkeeney Do you have a link that would explain how a c++ version can affect python compatibility? As far as I understand c++ code is just a dll. Thanks!
Is this restriction maybe just related to CPython? I think we might mix up something here. For instance, pybind, which is c++11 project can also target python 2.7. http://pybind11.readthedocs.io/en/stable/intro.html
@dkeeney Yes, one of the main features of pybind is to write bindings that work with 2.7 and the 3.x version of python. Write once run anywhere. ;-)