public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carlos.seo at linaro dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/114724] New: [Regression] libstdc++prettyprinters/debug.[cc|cxx11.cc] failing to build Date: Mon, 15 Apr 2024 17:30:52 +0000 [thread overview] Message-ID: <bug-114724-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114724 Bug ID: 114724 Summary: [Regression] libstdc++prettyprinters/debug.[cc|cxx11.cc] failing to build Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: carlos.seo at linaro dot org Target Milestone: --- The following tests are failing to build: === libstdc++ tests === Running libstdc++:libstdc++-prettyprinters/prettyprinters.exp ... UNRESOLVED: libstdc++-prettyprinters/debug.cc compilation failed to produce executable UNRESOLVED: libstdc++-prettyprinters/debug_cxx11.cc compilation failed to produce executable Possible culprit, according to the post-commit CI is: https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=c0419c024bf922128131671e40de0aed736e38ed CI logs: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binutils/sha1/c0419c024bf922128131671e40de0aed736e38ed/tcwg_gnu_native_check_gcc/master-aarch64/details.txt https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/1047/artifact/artifacts
next reply other threads:[~2024-04-15 17:30 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-15 17:30 carlos.seo at linaro dot org [this message] 2024-04-15 17:48 ` [Bug libstdc++/114724] " pinskia at gcc dot gnu.org 2024-04-15 18:01 ` carlos.seo at linaro dot org 2024-04-15 18:03 ` carlos.seo at linaro dot org 2024-04-16 2:52 ` sjames at gcc dot gnu.org 2024-04-16 2:53 ` sjames at gcc dot gnu.org
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=bug-114724-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).