public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/94262] New: valgrind error in get_pure_location
Date: Sun, 22 Mar 2020 17:32:27 +0000	[thread overview]
Message-ID: <bug-94262-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 94262
           Summary: valgrind error in get_pure_location
           Product: gcc
           Version: 10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

For testsuite file ./gcc.dg/visibility-10.c, compiled by recent gcc
trunk in a valgrind version, I get

./gcc.dg/visibility-10.c:19: error: expected ‘{’ at end of input
   19 | int l;
      |
==1850702== Conditional jump or move depends on uninitialised value(s)
==1850702==    at 0x14367D5: get_pure_location(line_maps*, unsigned int)
(line-map.c:322)
==1850702==    by 0xD4E4A7: get_pure_location (input.h:148)
==1850702==    by 0xD4E4A7: set_block(unsigned int, tree_node*) (tree.c:14835)
==1850702==    by 0x12E0DED: gimple_set_block (gimple.h:1865)

Command line is

$ /home/dcb/gcc/results/bin/gcc -c ./gcc.dg/visibility-10.c

             reply	other threads:[~2020-03-22 17:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-22 17:32 dcb314 at hotmail dot com [this message]
2020-03-22 17:53 ` [Bug c/94262] " marxin at gcc dot gnu.org
2020-03-22 18:07 ` jakub 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-94262-4@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).