On Thu, Apr 27, 2023 at 12:19 AM Dwight Kulkarni wrote:
>
> Your code is exactly what I had before. But I was getting that heap error. It
> only went away when I used NEW. I have never seen that before. I also don't
> like using NEW at all but it wasn't working.
convert_cryptopp_intege and
On Thu, Apr 27, 2023 at 12:19 AM Dwight Kulkarni wrote:
>
> Your code is exactly what I had before. But I was getting that heap error. It
> only went away when I used NEW. I have never seen that before. I also don't
> like using NEW at all but it wasn't working.
>
When moving an allocation
Hi Jeff,
Your code is exactly what I had before. But I was getting that heap error.
It only went away when I used NEW. I have never seen that before. I also
don't like using NEW at all but it wasn't working.
On Wednesday, April 26, 2023 at 11:21:46 PM UTC-4 Jeffrey Walton wrote:
> On Wed,
On Wed, Apr 26, 2023 at 11:16 PM Jeffrey Walton wrote:
>
> On Wed, Apr 26, 2023 at 6:13 PM Dwight Kulkarni wrote:
> >
> > I ran address sanitizer: Heap use after free is the problem. I had to use
> > the NEW operator to allocate the ram. What is weird is that usually it
> > will error out
On Wed, Apr 26, 2023 at 6:13 PM Dwight Kulkarni wrote:
>
> I ran address sanitizer: Heap use after free is the problem. I had to use
> the NEW operator to allocate the ram. What is weird is that usually it will
> error out right away after it goes out of scope, but this was delayed in
>
Hi Jeff,
I ran address sanitizer: Heap use after free is the problem. I had to use
the NEW operator to allocate the ram. What is weird is that usually it
will error out right away after it goes out of scope, but this was delayed
in recovering the memory, so it was working and then poof the
Hi Jeff,
I ran address sanitizer: Heap use after free is the problem. I had to use
the NEW operator to allocate the ram. What is weird is that usually it
will error out right away after it goes out of scope, but this was delayed
in recovering the memory, so it was working and then poof the
If you have the code with inline assembly for MacOS M1, I can test it.
> On Apr 25, 2023, at 22:39, Jeffrey Walton wrote:
>
>
>
> On Friday, March 31, 2023 at 1:44:41 AM UTC-4 Sam Van Gucht wrote:
> Hi everyone,
>
> We noticed AES GCM in significant slower on M1 compare to an Intel Mac.
