Re: CI Builds

[Sergio Durigan Junior <sergiodj@sergiodj.net>]

[-- 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 <jbglaw@lug-owl.de> 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@.

Thanks,

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

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