public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "userm57 at yahoo dot com" <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:42:44 +0000 [thread overview]
Message-ID: <bug-109927-4-tXWVhw7D68@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 #14 from Stan Johnson <userm57 at yahoo dot com> ---
I can try to capture the offending "cc1plus" and "as" processes just before the
compilation of gimple-match.cc fails in stage2; the output will look something
like this (for a different cc1plus process number 19431 that is currently
running):
# cat /proc/19431/maps
80000000-82027000 r-xp 00000000 08:05 1823425
/var/tmp/portage/sys-devel/gcc-13.1.1_p20230520/work/build/prev-gcc/cc1plus
82028000-8202a000 r--p 02028000 08:05 1823425
/var/tmp/portage/sys-devel/gcc-13.1.1_p20230520/work/build/prev-gcc/cc1plus
8202a000-82036000 rw-p 0202a000 08:05 1823425
/var/tmp/portage/sys-devel/gcc-13.1.1_p20230520/work/build/prev-gcc/cc1plus
82036000-82070000 rwxp 00000000 00:00 0 [heap]
82070000-82601000 rwxp 00000000 00:00 0 [heap]
c0000000-c0020000 r-xp 00000000 08:05 1682956 /lib/ld.so.1
c0020000-c0022000 r--p 00020000 08:05 1682956 /lib/ld.so.1
c0022000-c0023000 rw-p 00022000 08:05 1682956 /lib/ld.so.1
c0023000-c0026000 rw-p 00000000 00:00 0
c0028000-c0044000 r-xp 00000000 08:05 1515049 /usr/lib/libmpc.so.3.3.1
c0044000-c0045000 ---p 0001c000 08:05 1515049 /usr/lib/libmpc.so.3.3.1
c0045000-c0046000 r--p 0001b000 08:05 1515049 /usr/lib/libmpc.so.3.3.1
c0046000-c0047000 rw-p 0001c000 08:05 1515049 /usr/lib/libmpc.so.3.3.1
c0048000-c00b3000 r-xp 00000000 08:05 1672972 /usr/lib/libmpfr.so.6.2.0
c00b3000-c00b5000 ---p 0006b000 08:05 1672972 /usr/lib/libmpfr.so.6.2.0
c00b5000-c00b6000 r--p 0006b000 08:05 1672972 /usr/lib/libmpfr.so.6.2.0
c00b6000-c00b7000 rw-p 0006c000 08:05 1672972 /usr/lib/libmpfr.so.6.2.0
c00b8000-c0113000 r-xp 00000000 08:05 1515186 /usr/lib/libgmp.so.10.4.1
c0113000-c0115000 ---p 0005b000 08:05 1515186 /usr/lib/libgmp.so.10.4.1
c0115000-c0116000 r--p 0005b000 08:05 1515186 /usr/lib/libgmp.so.10.4.1
c0116000-c0117000 rw-p 0005c000 08:05 1515186 /usr/lib/libgmp.so.10.4.1
c0118000-c012a000 r-xp 00000000 08:05 411479 /lib/libz.so.1.2.13
c012a000-c012b000 ---p 00012000 08:05 411479 /lib/libz.so.1.2.13
c012b000-c012c000 r--p 00011000 08:05 411479 /lib/libz.so.1.2.13
c012c000-c012d000 rw-p 00012000 08:05 411479 /lib/libz.so.1.2.13
c012e000-c0172000 r-xp 00000000 08:05 1682625 /lib/libm.so.6
c0172000-c0173000 ---p 00044000 08:05 1682625 /lib/libm.so.6
c0173000-c0174000 r--p 00043000 08:05 1682625 /lib/libm.so.6
c0174000-c0176000 rw-p 00044000 08:05 1682625 /lib/libm.so.6
c0176000-c02df000 r-xp 00000000 08:05 1682906 /lib/libc.so.6
c02df000-c02e0000 ---p 00169000 08:05 1682906 /lib/libc.so.6
c02e0000-c02e2000 r--p 0016a000 08:05 1682906 /lib/libc.so.6
c02e2000-c02e6000 rw-p 0016c000 08:05 1682906 /lib/libc.so.6
c02e6000-c0ad2000 rw-p 00000000 00:00 0
c0ad5000-c25dd000 rw-p 00000000 00:00 0
ef91f000-ef948000 rw-p 00000000 00:00 0 [stack]
> Git checkout master
Thanks, I'll try compiling that version manually and also capture the relevant
/proc output.
next prev parent reply other threads:[~2023-05-23 18:42 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
2023-05-23 18:42 ` userm57 at yahoo dot com [this message]
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-tXWVhw7D68@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: link
Be 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).