public inbox for gcc-regression@sourceware.org help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com> To: ci_notify@linaro.org Cc: gcc-regression@gcc.gnu.org Subject: Re: [TCWG CI] Failure after gdb-12-branchpoint-3046-g969b9a36506: gas: re-work line number tracking for macros and their expansions Date: Wed, 14 Dec 2022 09:57:55 +0100 [thread overview] Message-ID: <87756439-57be-014f-9788-9243b306c564@suse.com> (raw) In-Reply-To: <1807487430.1182.1670975654754@jenkins.jenkins> On 14.12.2022 00:54, ci_notify@linaro.org wrote: > Failure after gdb-12-branchpoint-3046-g969b9a36506: gas: re-work line number tracking for macros and their expansions: > > Results changed to > -10 > # true: > 0 > # build_abe binutils: > 1 > # build_abe bootstrap_O3: > # FAILED > # First few build errors in logs: > # 00:08:36 make[3]: [Makefile:1818: armv8l-unknown-linux-gnueabihf/bits/largefile-config.h] Error 1 (ignored) > # 00:44:06 make[3]: [Makefile:1818: armv8l-unknown-linux-gnueabihf/bits/largefile-config.h] Error 1 (ignored) > # 01:01:09 make[3]: [Makefile:1818: armv8l-unknown-linux-gnueabihf/bits/largefile-config.h] Error 1 (ignored) > # 01:02:40 make[2]: *** [Makefile:25808: compare] Error 1 > # 01:02:40 make[1]: *** [Makefile:25788: stage3-bubble] Error 2 > # 01:02:40 make: *** [Makefile:1063: all] Error 2 All this allows me is to guess that there was a comparison failure of some of the generated binaries between stage2 and stage3. Would be nice if such a mail contained more helpful information. > * master-arm-bootstrap_O3 > ** Failure after gdb-12-branchpoint-3046-g969b9a36506: gas: re-work line number tracking for macros and their expansions: > ** https://ci.linaro.org/job/tcwg_gcc_bootstrap-build-master-arm-bootstrap_O3/561/ > > Bad build: https://ci.linaro.org/job/tcwg_gcc_bootstrap-build-master-arm-bootstrap_O3/561/artifact/artifacts Following this link allows me to prove the suspicion, but the artifacts don't include any object files, so I can't look at their differences. Re-creating the apparently problematic assembler input from gcc sources and passing it through the assembler multiple times doesn't yield any difference here. Hence I'm lost as to investigating this breakage, and I have the at least vague feeling that my change may merely have uncovered an issue which was latently there already before. Suggestions very welcome, Jan > Good build: https://ci.linaro.org/job/tcwg_gcc_bootstrap-build-master-arm-bootstrap_O3/560/artifact/artifacts > > Reproduce current build: > <cut> > mkdir -p investigate-binutils-969b9a36506bfb386f8ce30f88f1a6a6ebbaca6e > cd investigate-binutils-969b9a36506bfb386f8ce30f88f1a6a6ebbaca6e > > # Fetch scripts > git clone https://git.linaro.org/toolchain/jenkins-scripts > > # Fetch manifests for bad and good builds > mkdir -p bad/artifacts good/artifacts > curl -o bad/artifacts/manifest.sh https://ci.linaro.org/job/tcwg_gcc_bootstrap-build-master-arm-bootstrap_O3/561/artifact/artifacts/manifest.sh --fail > curl -o good/artifacts/manifest.sh https://ci.linaro.org/job/tcwg_gcc_bootstrap-build-master-arm-bootstrap_O3/560/artifact/artifacts/manifest.sh --fail > > # Reproduce bad build > (cd bad; ../jenkins-scripts/tcwg_gnu-build.sh ^^ true %%rr[top_artifacts] artifacts) > # Reproduce good build > (cd good; ../jenkins-scripts/tcwg_gnu-build.sh ^^ true %%rr[top_artifacts] artifacts) > </cut>
prev parent reply other threads:[~2022-12-14 8:58 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-13 23:54 ci_notify 2022-12-14 8:57 ` Jan Beulich [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: 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=87756439-57be-014f-9788-9243b306c564@suse.com \ --to=jbeulich@suse.com \ --cc=ci_notify@linaro.org \ --cc=gcc-regression@gcc.gnu.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: linkBe 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).