public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/29198] [Regression] specified bound 4294967295 may exceed maximum object size 2147483647
Date: Fri, 23 Dec 2022 21:42:59 +0000 [thread overview]
Message-ID: <bug-29198-4717-4LrR6WlADX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29198-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29198
--- Comment #6 from Mark Wielaard <mark at klomp dot org> ---
The patch to suppress this warning was pushed:
commit dac0515d825e788dec188fff4d5b9d4ac7383f33
Author: Mark Wielaard <mark@klomp.org>
Date: Tue May 31 11:00:06 2022 +0200
gdb: Always suppress stringop-overread warning in debuginfod-support.c
Just like on s390x with g++ 11.2.1 and ppc64le with g++ 11.3.1 g++ 11
on hppa produces a spurious warning for stringop-overread in
debuginfod_is_enabled for url_view. Just always suppress it on all
arches.
https://sourceware.org/bugzilla/show_bug.cgi?id=29198
gdb/ChangeLog:
* debuginfod-support.c (debuginfod_is_enabled): Always use
DIAGNOSTIC_IGNORE_STRINGOP_OVERREAD.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-12-23 21:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 19:11 [Bug compile/29198] New: " danglin at gcc dot gnu.org
2022-05-30 19:27 ` [Bug compile/29198] " mark at klomp dot org
2022-05-30 22:39 ` danglin at gcc dot gnu.org
2022-05-31 9:06 ` mark at klomp dot org
2022-06-06 13:31 ` [Bug build/29198] " tromey at sourceware dot org
2022-12-23 20:04 ` tromey at sourceware dot org
2022-12-23 21:26 ` dave.anglin at bell dot net
2022-12-23 21:42 ` mark at klomp dot org [this message]
2022-12-24 1:56 ` tromey at sourceware dot org
2022-12-24 10:43 ` mark at klomp dot 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-29198-4717-4LrR6WlADX@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: 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).