Possible leaks observed in GCC.

[Jonathan Wakely]

On Wed, 9 Dec 2020 at 12:53, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>
> On Wed, 9 Dec 2020 at 12:45, Tomar, Sourabh Singh via Gcc
> <gcc@gcc.gnu.org> wrote:
> >
> > Hi Folks,
> >
> > I observed some leaks using valgrind while compiling a sample program using GCC.
>
> This seems more appropriate for gcc-help@gcc.gnu.org instead.
>
> > Could anyone aware of these details provide any insights to these leaks ?
>
> You've provided no information that can tell us anything for sure, but
> these are probably leaks caused by your code. You can use valgrind to
> find them.

Oh sorry, I missed that you're running gcc itself under valgrind.
Those are probably intentional, because GCC uses garbage collection
for some of its allocations, and knows that it's not going to be a
long-running process, so it will exit fairly soon and all memory will
be freed on exit.

Using --leak-check=full would still give you more information.