public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamesallwright at yahoo dot co.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/105013] Valgrind reports accessing uninitialized memory when -O2 option is used
Date: Tue, 22 Mar 2022 18:40:58 +0000	[thread overview]
Message-ID: <bug-105013-4-7mzCKjuXnT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105013-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105013

--- Comment #2 from James Allwright <jamesallwright at yahoo dot co.uk> ---
Here is the valgrind output

valgrind ./bug
==2490== Memcheck, a memory error detector
==2490== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==2490== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==2490== Command: ./bug
==2490== 
out = 
command = 
==2490== Conditional jump or move depends on uninitialised value(s)
==2490==    at 0x1092DB: example_func (bug.c:37)
==2490==    by 0x1090D3: main (bug.c:44)
==2490== 
==2490== 
==2490== HEAP SUMMARY:
==2490==     in use at exit: 0 bytes in 0 blocks
==2490==   total heap usage: 1 allocs, 1 frees, 1,024 bytes allocated
==2490== 
==2490== All heap blocks were freed -- no leaks are possible
==2490== 
==2490== Use --track-origins=yes to see where uninitialised values come from
==2490== For lists of detected and suppressed errors, rerun with: -s
==2490== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

  parent reply	other threads:[~2022-03-22 18:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22  9:08 [Bug c/105013] New: " jamesallwright at yahoo dot co.uk
2022-03-22  9:47 ` [Bug c/105013] " marxin at gcc dot gnu.org
2022-03-22 18:40 ` jamesallwright at yahoo dot co.uk [this message]
2022-03-23  8:54 ` marxin at gcc dot gnu.org
2022-03-23 14:35 ` jamesallwright at yahoo dot co.uk
2022-03-23 14:37 ` marxin at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-105013-4-7mzCKjuXnT@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).