From: Simon Marchi <simark@simark.ca>
To: Mark Wielaard <mark@klomp.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware)
Date: Tue, 3 May 2022 20:51:58 -0400 [thread overview]
Message-ID: <59c54104-42e9-42da-b2f0-9ac455426554@simark.ca> (raw)
In-Reply-To: <YnG8lzwMZwRn+wAo@wildebeest.org>
On 2022-05-03 19:36, Mark Wielaard wrote:
> Hi Simon,
>
> Moved to gdb-patches, now that we have an approach and concrete patch.
>
> On Tue, May 03, 2022 at 11:41:33AM -0400, Simon Marchi wrote:
>> If it's really just the diagnostic that is bogus, my preference would be
>> to try to silence the diagnostic and not modify the code.
>>
>> It would require adding a DIAGNOSTIC_IGNORE_STRINGOP_OVERREAD to
>> include/diagnostics.h.
>>
>> I would also limit the disabling to just that arch
>
> OK, how about the attached? Build on fedora/s390x and debian/aarch64.
>
> Thanks,
>
> Mark
Hi Mark,
This is ok. Note that you don't need the ChangeLog entry for the GDB change,
but you do for the include/ change.
Simon
next prev parent reply other threads:[~2022-05-04 0:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YmbmguMq2Aq+BzAX@wildebeest.org>
[not found] ` <524b04b7-a78c-7aae-4605-b40f61e6830c@arm.com>
[not found] ` <YmhzY4c3pOPLRgSw@wildebeest.org>
[not found] ` <16fe426d-c436-f030-dc43-0e81e7f0e853@arm.com>
[not found] ` <20220428141957.GB23335@gnu.wildebeest.org>
[not found] ` <m3zgk5clif.fsf@fitzsim.org>
[not found] ` <20220428162803.GD23335@gnu.wildebeest.org>
[not found] ` <20220429200422.GB7305@gnu.wildebeest.org>
[not found] ` <20220501194445.GB30898@gnu.wildebeest.org>
[not found] ` <f12d07da-8692-5321-95e1-8b2fb5a84cf1@simark.ca>
2022-05-03 23:36 ` Mark Wielaard
2022-05-04 0:51 ` Simon Marchi [this message]
2022-06-15 7:33 ` Tom de Vries
2022-06-15 11:09 ` Mark Wielaard
2022-06-15 14:38 ` Mark Wielaard
2022-06-15 19:18 ` Martin Liška
2022-06-15 19:48 ` Mark Wielaard
2022-06-16 4:09 ` Martin Liška
2022-06-16 21:19 ` Mark Wielaard
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=59c54104-42e9-42da-b2f0-9ac455426554@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).