public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/105114] [12 regression] contrib/gcc_update hangs Date: Thu, 31 Mar 2022 08:12:17 +0000 [thread overview] Message-ID: <bug-105114-4-8kbmXbSZQG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105114-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105114 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- This is just weird, all the files in question: gcc/config/loongarch/loongarch-str.h gcc/config/loongarch/genopts/genstr.sh gcc/config/loongarch/genopts/loongarch-string gcc/config/loongarch/loongarch.opt gcc/config/loongarch/genopts/loongarch.opt.in have been added in the same commit as contrib/gcc_update has been updated. So, if you still have a tree where it hangs, can you ls -l gcc/config/loongarch/loongarch-str.h gcc/config/loongarch/genopts/genstr.sh gcc/config/loongarch/genopts/loongarch-string gcc/config/loongarch/loongarch.opt gcc/config/loongarch/genopts/loongarch.opt.in ?
next prev parent reply other threads:[~2022-03-31 8:12 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-30 20:56 [Bug other/105114] New: " seurer at gcc dot gnu.org 2022-03-31 7:06 ` [Bug other/105114] " rguenth at gcc dot gnu.org 2022-03-31 8:12 ` jakub at gcc dot gnu.org [this message] 2022-03-31 12:33 ` seurer at gcc dot gnu.org 2022-03-31 12:51 ` jakub at gcc dot gnu.org 2022-03-31 13:48 ` seurer at gcc dot gnu.org 2022-03-31 13:54 ` seurer at gcc dot gnu.org 2022-03-31 14:08 ` schwab@linux-m68k.org 2022-03-31 14:27 ` jakub at gcc dot gnu.org 2022-03-31 16:59 ` joseph at codesourcery dot com 2022-03-31 17:19 ` jakub at gcc dot gnu.org 2022-03-31 17:24 ` cvs-commit at gcc dot gnu.org 2022-03-31 17:26 ` jakub 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-105114-4-8kbmXbSZQG@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).