From: Simon Marchi <simark@simark.ca>
To: Mark Wielaard <mark@klomp.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Workaround stringop-overread warning in debuginfod-support.c on powerpc64
Date: Wed, 11 May 2022 20:49:22 -0400 [thread overview]
Message-ID: <e5fb1b8e-d86d-fd88-e3f2-b29f151d5264@simark.ca> (raw)
In-Reply-To: <20220511225219.119067-1-mark@klomp.org>
On 2022-05-11 18:52, Mark Wielaard wrote:
> Just like on s390x with g++ 11.2.1, ppc64le with g++ 11.3.1 produces a
> spurious warning for stringop-overread in debuginfod_is_enabled
> for url_view. Also suppress it on powerpc64.
>
> gdb/ChangeLog:
>
> * debuginfod-support.c (debuginfod_is_enabled): Use
> DIAGNOSTIC_IGNORE_STRINGOP_OVERREAD on powerpc64.
LGTM.
> ---
>
> Found with the new fedora-ppc64le builder:
> https://builder.sourceware.org/buildbot/#/builders/gdb-fedora-ppc64le
>
> Alternatively we could just suppress this warning for any architecture.
Let's make a deal, if you find a 3rd architecture where this is the case
we do that, alright? ;)
Simon
next prev parent reply other threads:[~2022-05-12 0:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 22:52 Mark Wielaard
2022-05-12 0:49 ` Simon Marchi [this message]
2022-05-31 9:05 ` Mark Wielaard
2022-05-31 9:46 ` Pedro Alves
2022-05-31 10:51 ` Mark Wielaard
2022-06-06 11:27 ` Mark Wielaard
2022-06-06 16:42 ` Pedro Alves
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=e5fb1b8e-d86d-fd88-e3f2-b29f151d5264@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=mark@klomp.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).