Re: Possible leaks observed in GCC.

2020-12-09 Thread Paul Floyd
On 12/9/20 1:44 PM, Tomar, Sourabh Singh via Gcc wrote: Hi Folks, I observed some leaks using valgrind while compiling a sample program using GCC. ==32090== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info Also 3.13 is rather old. 3.16.1 is the current release - not that

Re: Possible leaks observed in GCC.

2020-12-09 Thread Jakub Jelinek via Gcc
On Wed, Dec 09, 2020 at 12:55:40PM +, Jonathan Wakely via Gcc wrote: > > > I observed some leaks using valgrind while compiling a sample program > > > using GCC. > > > > This seems more appropriate for gcc-h...@gcc.gnu.org instead. > > > > > Could anyone aware of these details provide any insi

Re: Possible leaks observed in GCC.

2020-12-09 Thread Jonathan Wakely via Gcc
On Wed, 9 Dec 2020 at 12:53, Jonathan Wakely wrote: > > On Wed, 9 Dec 2020 at 12:45, Tomar, Sourabh Singh via Gcc > wrote: > > > > Hi Folks, > > > > I observed some leaks using valgrind while compiling a sample program using > > GCC. > > This seems more appropriate for gcc-h...@gcc.gnu.org inste

Re: Possible leaks observed in GCC.

2020-12-09 Thread Paul Floyd
On 12/9/20 1:44 PM, Tomar, Sourabh Singh via Gcc wrote: Hi Folks, I observed some leaks using valgrind while compiling a sample program using GCC. Could anyone aware of these details provide any insights to these leaks ? ==32090== Rerun with --leak-check=full to see details of leaked memory

Re: Possible leaks observed in GCC.

2020-12-09 Thread Jonathan Wakely via Gcc
On Wed, 9 Dec 2020 at 12:45, Tomar, Sourabh Singh via Gcc wrote: > > Hi Folks, > > I observed some leaks using valgrind while compiling a sample program using > GCC. This seems more appropriate for gcc-h...@gcc.gnu.org instead. > Could anyone aware of these details provide any insights to these