public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug build/28613] error: array subscript 19 is outside array bounds of ‘void [136]’ [-Werror=array-bounds] Date: Mon, 22 Nov 2021 16:15:47 +0000 [thread overview] Message-ID: <bug-28613-4717-axK6ak5aST@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28613-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28613 Martin Sebor <msebor at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msebor at gmail dot com --- Comment #2 from Martin Sebor <msebor at gmail dot com> --- I don';t see the warning in my build log. My latest Binutils/GDB build (today's top of trunk with today's GCC) shows the warnings below. Because of their large number I usually just check for obvious regressions. Diagnostic Count Unique Files -Wimplicit-function-declaration 88 62 10 -Wmaybe-uninitialized 43 37 23 -Wincompatible-pointer-types 42 42 1 -Wmissing-prototypes 25 25 5 -Wpointer-to-int-cast 10 10 1 -Wint-to-pointer-cast 9 9 1 -Walloc-zero 8 3 3 -Wconflicts-sr 5 5 5 -Wpointer-sign 4 4 2 -Wstrict-aliasing 3 3 1 -Wconflicts-rr 1 1 1 (If you see a warning that you believe is a false positive that's not tracked in GCC Bugzilla yet please submit a bug there with the usual details.) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-11-22 16:15 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-22 9:45 [Bug build/28613] New: " mliska at suse dot cz 2021-11-22 9:48 ` [Bug build/28613] " mliska at suse dot cz 2021-11-22 16:15 ` msebor at gmail dot com [this message] 2021-11-23 8:43 ` mliska at suse dot cz
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-28613-4717-axK6ak5aST@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).