public inbox for
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <>
To: Jan-Benedict Glaw <>
Subject: Re: CI Builds
Date: Sun, 01 Aug 2021 19:35:09 -0400	[thread overview]
Message-ID: <878s1kg2mq.fsf@paluero> (raw)
In-Reply-To: <> (Jan-Benedict Glaw's message of "Sat, 31 Jul 2021 23:18:40 +0200")

[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]

On Saturday, July 31 2021, Jan-Benedict Glaw wrote:

> Hi!
> On Mon, 2021-07-26 23:11:01 +0200, Jan-Benedict Glaw <> wrote:
>> Hi!
>> I'm running some CI builds and noticed that, when building GDB with
>> quite recent GCC versions, it breaks.
>> With ie. this "gcc-snapshot" GCC from Debian:
>> /usr/lib/gcc-snapshot/bin/gcc --version
>> gcc (Debian 20210630-1) 12.0.0 20210630 (experimental) [master revision 6bf383c37e6:93c270320bb:35da8a98026849bd20d16bbf9210ac1d0b44ea6a]
> [...]
> I just wanted to add a few thoughts.
>   There's this machine running, doing test compiles for
> Binutils/GAS/GDB as well as GCC, Linux kernel, SIMH simulator and
> NetBSD (cross-compiled from Linux and from a NetBSD host running in
> KVM.) I'm usually building with gcc-snapshot (except Linux kernel,
> which cross-compiles from my last matching GCC build for that target,
> so it's nearly master.)
>   When I detect issues like this (either individual targets or global
> breakages like this non-null attribution issue), shall I report them
> to the GDB list? Open a ticket? Most of the time, I think I'd be able
> to pin-point a causing commit.

If you're able to pinpoint a commit, then the best IMO would be to reply
to the email thread where the patch was discussed (on gdb-patches@).
This is what I was doing when I was reporting regressions on behalf of
the GDB Buildbot.  Not all developers pay attention to gdb@.


GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2021-08-01 23:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-26 21:11 Building with recent GCC versions: gdbsupport/gdb_assert.h:35:4: error: 'nonnull' argument 'filename' compared to NULL [-Werror=nonnull-compare] Jan-Benedict Glaw
2021-07-27 10:03 ` Andrew Burgess
2021-07-27 10:44   ` Tom de Vries
2021-07-27 11:35     ` Andrew Burgess
2021-07-27 11:49       ` Tom de Vries
2021-07-27 13:38         ` Tom de Vries
2021-07-28  8:37           ` Andrew Burgess
2021-07-31 21:18 ` CI Builds (was: Building with recent GCC versions: gdbsupport/gdb_assert.h:35:4: error: 'nonnull' argument 'filename' compared to NULL [-Werror=nonnull-compare]) Jan-Benedict Glaw
2021-08-01 23:35   ` Sergio Durigan Junior [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878s1kg2mq.fsf@paluero \ \ \ \

* 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).