From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id NK2dJMwvB2E0MgAAWB0awg (envelope-from ) for ; Sun, 01 Aug 2021 19:35:40 -0400 Received: by simark.ca (Postfix, from userid 112) id 85FD51EDFB; Sun, 1 Aug 2021 19:35:40 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 590A41E79C for ; Sun, 1 Aug 2021 19:35:36 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 7DAA0383F42B for ; Sun, 1 Aug 2021 23:35:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7DAA0383F42B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1627860935; bh=hahwb0GX+ozhT9oqjzVVivL97nMeWgxZFW7yrgavIQ8=; h=To:Subject:References:Date:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=kCjv1hU+wSfY9dZXc3exqepXDuLUobjdz9J78UHVljgf/6IfKSb4IztQn3HgIrJ8t qqJE/wK/XXYPsGDC360SxnVXcE57Bp8+KH2tm4pB22Rxv4Vu30uQH8R+9Qq/CE/44R N5B/5NDE7aqnGQ5xaNwSrgZU2XQLy5KVHP4ChDLA= Received: from mail.sergiodj.net (mail.sergiodj.net [IPv6:2607:5300:60:3666::3]) by sourceware.org (Postfix) with ESMTPS id 68D5B386F41A for ; Sun, 1 Aug 2021 23:35:10 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 68D5B386F41A Received: from localhost (bras-base-toroon1016w-grc-33-76-64-54-140.dsl.bell.ca [76.64.54.140]) by mail.sergiodj.net (Postfix) with ESMTPSA id B1EA9A0088; Sun, 1 Aug 2021 19:35:09 -0400 (EDT) To: Jan-Benedict Glaw Subject: Re: CI Builds References: <20210726211101.ivychvbfgaafxjtz@lug-owl.de> <20210731211840.4khiwd5rqn22xgrg@lug-owl.de> X-URL: http://blog.sergiodj.net Date: Sun, 01 Aug 2021 19:35:09 -0400 In-Reply-To: <20210731211840.4khiwd5rqn22xgrg@lug-owl.de> (Jan-Benedict Glaw's message of "Sat, 31 Jul 2021 23:18:40 +0200") Message-ID: <878s1kg2mq.fsf@paluero> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Sergio Durigan Junior via Gdb Reply-To: Sergio Durigan Junior Cc: gdb@sourceware.org Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Saturday, July 31 2021, Jan-Benedict Glaw wrote: > Hi! > > On Mon, 2021-07-26 23:11:01 +0200, Jan-Benedict Glaw = wrote: >> Hi! >>=20 >> I'm running some CI builds and noticed that, when building GDB with >> quite recent GCC versions, it breaks. >>=20 >> With ie. this "gcc-snapshot" GCC from Debian: >>=20 >> /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, =2D-=20 Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible https://sergiodj.net/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEI3pUsQKHKL8A7zH00Ot2KGX8XjYFAmEHL60ACgkQ0Ot2KGX8 XjYRWhAAmamno7zjbcEDBG4DBDrDcuVp/qpP5WeTW0dDQfO/SypCjW3uZxf1HGxR VoqFb5CgYc11mAbAbA1mbKKecsBLyYH+Zq2684tZytkjgjt+uKyUVnxl/SejVDpq WMox1wUJUJIbhm94WoX8p6GxKWqDRT1UFsF+B4WCt2Q5DZo9VWTgeSMcuZXpmVHS t0FnFwYbW66oZ1JQhoQ3DipJbHGtorWHZCtN8FrmlI3UaqJaKt7UrRD4GTJRo0HO NPLTEEK6ArgGwunAIIh6QnbG1JO6MOM1Hy1vV5LL5zDEV1gt9RKcTSco3wOqJvXm naG9XxPdqDEsvVUdzmmLdG6cV55KjJGr9AC4+GqxSoT9xssUv1AJwgrlGR40YnpB w0A5WLWeu9q7fLKvNawCAzCpnlqv97N1icNs5PT7tWjynDPBCLGSFWZotsfCtWXA bwiWm4lPxBXwhrE93r4094vZXUII26olU+GG/DVwOQ+0Q2KfzjRKiRht3dsSq5M3 7OwDis+LYopYLp7ZpKui5QcBzbrWTi1sEWB+kkWJrlmN++CYcv0YFrLOpFizVMd4 dovAonyL14X2BytsEv1JIHtE1dC69XWqRyekwsejCRgMgqaOBaCDS+Kkuzx1doHn 9wLkneWmOtvmlKEeRjzpVtHjtndH9fgmRE64z70I5iCkDNg6UOI= =aOsw -----END PGP SIGNATURE----- --=-=-=--