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/101176] New: valgrind error for c-c++-common/builtin-has-attribute.c Date: Wed, 23 Jun 2021 06:55:47 +0000 [thread overview] Message-ID: <bug-101176-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101176 Bug ID: 101176 Summary: valgrind error for c-c++-common/builtin-has-attribute.c Product: gcc Version: 12.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 the gcc testsuite file c-c++-common/builtin-has-attribute.c and a recent build of gcc trunk with valgrind, I get: ./c-c++-common/builtin-has-attribute.c:31:32: error: ‘foobar’ undeclared (first use in this function) 31 | b = __builtin_has_attribute (foobar, aligned); /* { dg-error ".foobar . \(undeclared|was not declared\)" } */ | ^~~~~~ ==104199== Use of uninitialised value of size 8 ==104199== at 0x16EDF70: htab_find_slot_with_hash (hashtab.c:654) ==104199== by 0x169B7CD: get_combined_adhoc_loc(line_maps*, unsigned int, sou rce_range, void*) (line-map.c:208) Since this valgrind error is for C code with errors in it, I think this is reduced priority.
next reply other threads:[~2021-06-23 6:55 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-23 6:55 dcb314 at hotmail dot com [this message] 2021-06-23 21:59 ` [Bug c/101176] " jakub at gcc dot gnu.org 2021-06-24 13:58 ` cvs-commit at gcc dot gnu.org 2021-06-24 14:03 ` jakub at gcc dot gnu.org 2021-07-18 23:28 ` cvs-commit at gcc dot gnu.org 2022-05-10 8:19 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:20 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:36 ` jakub at gcc dot gnu.org 2022-10-28 23:26 ` pinskia 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-101176-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: linkBe 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).