Thread overview
[Issue 16280] -profile=gc wrongly reports allocation when using reserve on dynamic arrays
Jul 14, 2016
Cédric Picard
Apr 20, 2017
Leandro Lucarella
Apr 20, 2017
Leandro Lucarella
Nov 09, 2022
RazvanN
July 14, 2016
https://issues.dlang.org/show_bug.cgi?id=16280

--- Comment #1 from Cédric Picard <cpicard@openmailbox.org> ---
I should mention that this was done with DMD32 2.071.1 on GNU/Linux

--
April 20, 2017
https://issues.dlang.org/show_bug.cgi?id=16280

Leandro Lucarella <leandro.lucarella@sociomantic.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |leandro.lucarella@sociomant
                   |                            |ic.com
           See Also|                            |https://issues.dlang.org/sh
                   |                            |ow_bug.cgi?id=17294

--
April 20, 2017
https://issues.dlang.org/show_bug.cgi?id=16280

Leandro Lucarella <leandro.lucarella@sociomantic.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://issues.dlang.org/sh
                   |                            |ow_bug.cgi?id=15481

--
November 09, 2022
https://issues.dlang.org/show_bug.cgi?id=16280

RazvanN <razvan.nitu1305@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |razvan.nitu1305@gmail.com
         Resolution|---                         |WORKSFORME

--- Comment #2 from RazvanN <razvan.nitu1305@gmail.com> ---
I am getting:

capacity: 63
reallocation occurred: 63
reallocation occurred: 91
bytes allocated, allocations, type, function, file:line
            880               2 int[] test.append test.d:20

So it seems that this issue has been fixed.

--