In the words of Nick Danger: "You just saved me a lot of investigative
work."
Thank you so much.
Bob D.
-----Original Message-----
From: Jakub Jelinek <ja...@redhat.com>
Sent: Wednesday, January 10, 2024 15:51
To: Robert Dubner <rdub...@symas.com>
Cc: 'GCC Mailing List' <gcc@gcc.gnu.org>
Subject: Re: I am causing valgrind errors...
On Wed, Jan 10, 2024 at 02:47:08PM -0600, Robert Dubner wrote:
> Here's the thing: when I run valgrind on the compilation -- not on
> the executable, but on the compiler with the COBOL front end -- I am
> getting a bunch of errors that look like variations of this:
>
> ==1232157== Command: /home/bob/repos/gcc-cobol/build/gcc/cobol1
> playpen.cbl -quiet -dumpbase
> playpen.cbl -mtune=generic -march=x86-64 -ggdb -O0 -o playpen.s -cmain
> ==1232157== ==1232157== Conditional jump or move depends on
> uninitialised value(s)
> ==1232157== at 0xABA0CB: sparseset_bit_p (sparseset.h:146)
> ==1232157== by 0xABA0CB: mark_pseudo_regno_live(int)
(ira-lives.cc:326)
> ==1232157== by 0xABBDC0: process_bb_node_lives(ira_loop_tree_node*)
That is normal and not a bug.
If you want to avoid that, you need to configure the compiler with
--enable-valgrind-annotations (and have valgrind development installed
before you configure/build).
Jakub
