public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109927] Bootstrap fails for m68k in stage2 compilation of gimple-match.cc Date: Tue, 23 May 2023 18:24:20 +0000 [thread overview] Message-ID: <bug-109927-4-9ZxWUvUURC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109927-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109927 --- Comment #13 from rguenther at suse dot de <rguenther at suse dot de> --- > Am 23.05.2023 um 19:44 schrieb userm57 at yahoo dot com <gcc-bugzilla@gcc.gnu.org>: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109927 > > --- Comment #12 from Stan Johnson <userm57 at yahoo dot com> --- >> That’s indeed unhelpful. Cat /proc/maps of some executable might help > > Sorry, I don't know how to do that. I don't see /proc/maps. Try /proc/1/maps It’s a file in the per process directories > Regarding downloading mainline gcc-14, it's not at ftp.gnu.org. I tried the > following, but I must be using the wrong repository. Please advise on where I > should find gcc-14. > > $ git clone git://gcc.gnu.org/git/gcc.git > $ cd gcc > $ git reset --hard > HEAD is now at 0d2ab259bc5 Improve cost computation for single-bit bit > insertions. > $ git checkout releases/gcc-14 > error: pathspec 'releases/gcc-14' did not match any file(s) known to git > $ git checkout releases/gcc-13 > Already on 'releases/gcc-13' > Your branch is up to date with 'origin/releases/gcc-13'. > $ git checkout mainline/gcc-14 > error: pathspec 'mainline/gcc-14' did not match any file(s) known to git Git checkout master Should do what I meant
next prev parent reply other threads:[~2023-05-23 18:24 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-22 1:32 [Bug bootstrap/109927] New: " userm57 at yahoo dot com 2023-05-22 3:04 ` [Bug target/109927] " pinskia at gcc dot gnu.org 2023-05-22 6:25 ` xry111 at gcc dot gnu.org 2023-05-22 8:23 ` rguenth at gcc dot gnu.org 2023-05-23 0:09 ` userm57 at yahoo dot com 2023-05-23 5:32 ` sjames at gcc dot gnu.org 2023-05-23 15:00 ` userm57 at yahoo dot com 2023-05-23 15:29 ` rguenth at gcc dot gnu.org 2023-05-23 16:18 ` userm57 at yahoo dot com 2023-05-23 16:58 ` rguenther at suse dot de 2023-05-23 17:28 ` userm57 at yahoo dot com 2023-05-23 17:35 ` rguenther at suse dot de 2023-05-23 17:44 ` userm57 at yahoo dot com 2023-05-23 18:24 ` rguenther at suse dot de [this message] 2023-05-23 18:42 ` userm57 at yahoo dot com 2023-05-23 19:04 ` schwab@linux-m68k.org 2023-05-24 6:54 ` rguenth at gcc dot gnu.org 2023-05-24 7:59 ` schwab@linux-m68k.org 2023-05-24 23:19 ` userm57 at yahoo dot com 2023-05-25 7:24 ` rguenther at suse dot de 2023-05-25 7:41 ` sjames at gcc dot gnu.org 2023-05-25 7:47 ` rguenther at suse dot de 2023-07-27 9:48 ` sjames at gcc dot gnu.org 2023-07-28 7:50 ` rguenth 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-109927-4-9ZxWUvUURC@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).