Re: Directly accessing underlying memory for image

Subject: Re: Directly accessing underlying memory for image
From: Mateusz Loskot (mateusz_at_[hidden])
Date: 2019-05-07 07:34:47

On Mon, 6 May 2019 at 21:25, Olzhas Zhumabek
<anonymous.from.applecity_at_[hidden]> wrote:
> I found the problem. I just had to change this line:
>
> auto end = std::addressof(input_view(input_view.width() - 1,
> input_view.height() - 1));
>
> into this
>
> auto end = std::addressof(input_view(input_view.width() - 1,
> input_view.height() - 1)) + 1;

Good catch.

> The end pointer was off by one. I will post my findings and code that I
> used for benchmarking shortly on the issue page
> <https://github.com/boostorg/gil/issues/234>.

I responded briefly.
First, I suggest to use the develop branch.

Since you are using Visual Studio, you should be able to run your benchmark
under the performance profiler and see where the hot spots are.

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net