public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc_bugzilla at axeitado dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/100486] Ada build fails for 32bit Windows
Date: Mon, 18 Oct 2021 13:24:12 +0000 [thread overview]
Message-ID: <bug-100486-4-uPILr1p41D@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100486-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100486
--- Comment #66 from Óscar Fuentes <gcc_bugzilla at axeitado dot com> ---
(In reply to Eric Botcazou from comment #65)
> Thanks. Do you still have this line:
>
> 00000000 r .eh_frame
>
> for crtend.o of the GCC 10 compiler after the grep mess was resolved? Do
> you have the same line for the crtend.o of the GCC 11 compiler?
The problem with grep didn't affect my gcc 10 install because it was built with
grep 3.0, so crtend.o didn't change. Here it is again for completeness:
$ for f in `find /mingw32 -name crtend.o` ; do echo $f && nm $f ; done
/mingw32/lib/gcc/i686-w64-mingw32/10.3.0/crtend.o
00000000 b .bss
00000000 d .ctors.65535
00000000 d .data
00000000 r .eh_frame
00000000 r .rdata$zzz
00000000 t .text
00000000 t .text.startup
00000000 r ___FRAME_END__
U ___gcc_register_frame
00000000 t _register_frame_ctor
Now, these are the crtend.o created in the gcc 11.2 build directory before it
failed at a-except.o (this is also with grep 3.0, while in comment#29 was with
the botched grep 3.6, but I see no differences):
$ for f in `find
/d/dev/other/MINGW-packages/mingw-w64-gcc/src/build-i686-w64-mingw32 -name
crtend.o` ; do echo $f && nm $f ; done
/d/dev/other/MINGW-packages/mingw-w64-gcc/src/build-i686-w64-mingw32/prev-gcc/crtend.o
00000000 b .bss
00000000 d .ctors.65535
00000000 d .data
00000000 r .eh_frame
00000000 r .rdata$zzz
00000000 t .text
00000000 r ___FRAME_END__
U ___gcc_register_frame
00000000 t _register_frame_ctor
/d/dev/other/MINGW-packages/mingw-w64-gcc/src/build-i686-w64-mingw32/prev-i686-w64-mingw32/libgcc/crtend.o
00000000 b .bss
00000000 d .ctors.65535
00000000 d .data
00000000 r .eh_frame
00000000 r .rdata$zzz
00000000 t .text
00000000 r ___FRAME_END__
U ___gcc_register_frame
00000000 t _register_frame_ctor
Note that, as before, .text.startup is present in gcc-10 but missing in gcc-11
crtend.o.
next prev parent reply other threads:[~2021-10-18 13:24 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-08 12:22 [Bug ada/100486] New: " reiter.christoph at gmail dot com
2021-05-08 14:26 ` [Bug ada/100486] " ebotcazou at gcc dot gnu.org
2021-05-10 20:30 ` ofv at wanadoo dot es
2021-07-02 8:36 ` ebotcazou at gcc dot gnu.org
2021-07-03 3:42 ` ofv at wanadoo dot es
2021-07-03 3:58 ` ofv at wanadoo dot es
2021-07-03 7:27 ` ebotcazou at gcc dot gnu.org
2021-07-03 23:14 ` ofv at wanadoo dot es
2021-07-04 9:10 ` ebotcazou at gcc dot gnu.org
2021-07-04 13:39 ` ofv at wanadoo dot es
2021-07-04 14:43 ` ofv at wanadoo dot es
2021-07-04 17:15 ` ebotcazou at gcc dot gnu.org
2021-07-04 18:35 ` ofv at wanadoo dot es
2021-07-05 8:59 ` ralphengels at gmail dot com
2021-07-28 9:02 ` ebotcazou at gcc dot gnu.org
2021-07-30 7:49 ` reiter.christoph at gmail dot com
2021-10-10 2:41 ` gcc_bugzilla at axeitado dot com
2021-10-10 7:59 ` ebotcazou at gcc dot gnu.org
2021-10-10 16:50 ` gcc_bugzilla at axeitado dot com
2021-10-10 16:54 ` gcc_bugzilla at axeitado dot com
2021-10-11 7:51 ` ebotcazou at gcc dot gnu.org
2021-10-11 13:17 ` gcc_bugzilla at axeitado dot com
2021-10-11 14:11 ` ebotcazou at gcc dot gnu.org
2021-10-11 14:51 ` gcc_bugzilla at axeitado dot com
2021-10-11 15:05 ` gcc_bugzilla at axeitado dot com
2021-10-15 13:31 ` ebotcazou at gcc dot gnu.org
2021-10-15 14:05 ` gcc_bugzilla at axeitado dot com
2021-10-15 14:53 ` ebotcazou at gcc dot gnu.org
2021-10-15 18:55 ` ebotcazou at gcc dot gnu.org
2021-10-15 20:48 ` gcc_bugzilla at axeitado dot com
2021-10-15 21:44 ` ebotcazou at gcc dot gnu.org
2021-10-15 22:01 ` gcc_bugzilla at axeitado dot com
2021-10-15 22:50 ` ebotcazou at gcc dot gnu.org
2021-10-15 22:58 ` ebotcazou at gcc dot gnu.org
2021-10-15 23:07 ` ebotcazou at gcc dot gnu.org
2021-10-15 23:08 ` gcc_bugzilla at axeitado dot com
2021-10-15 23:12 ` gcc_bugzilla at axeitado dot com
2021-10-15 23:18 ` ebotcazou at gcc dot gnu.org
2021-10-15 23:28 ` gcc_bugzilla at axeitado dot com
2021-10-15 23:29 ` ebotcazou at gcc dot gnu.org
2021-10-15 23:30 ` ebotcazou at gcc dot gnu.org
2021-10-15 23:56 ` gcc_bugzilla at axeitado dot com
2021-10-16 0:04 ` ebotcazou at gcc dot gnu.org
2021-10-16 0:08 ` gcc_bugzilla at axeitado dot com
2021-10-16 5:19 ` reiter.christoph at gmail dot com
2021-10-16 7:55 ` ebotcazou at gcc dot gnu.org
2021-10-16 8:05 ` reiter.christoph at gmail dot com
2021-10-16 8:14 ` ebotcazou at gcc dot gnu.org
2021-10-16 8:20 ` reiter.christoph at gmail dot com
2021-10-16 8:36 ` ebotcazou at gcc dot gnu.org
2021-10-16 11:36 ` ebotcazou at gcc dot gnu.org
2021-10-16 12:33 ` reiter.christoph at gmail dot com
2021-10-16 22:09 ` reiter.christoph at gmail dot com
2021-10-17 2:17 ` gcc_bugzilla at axeitado dot com
2021-10-17 11:00 ` ebotcazou at gcc dot gnu.org
2021-10-17 13:43 ` gcc_bugzilla at axeitado dot com
2021-10-18 7:12 ` charlet at gcc dot gnu.org
2021-10-18 8:00 ` ebotcazou at gcc dot gnu.org
2021-10-18 8:05 ` ebotcazou at gcc dot gnu.org
2021-10-18 8:08 ` charlet at gcc dot gnu.org
2021-10-18 8:35 ` ebotcazou at gcc dot gnu.org
2021-10-18 8:45 ` charlet at gcc dot gnu.org
2021-10-18 10:49 ` ebotcazou at gcc dot gnu.org
2021-10-18 10:57 ` charlet at gcc dot gnu.org
2021-10-18 11:54 ` gcc_bugzilla at axeitado dot com
2021-10-18 12:43 ` ebotcazou at gcc dot gnu.org
2021-10-18 13:24 ` gcc_bugzilla at axeitado dot com [this message]
2021-10-18 15:18 ` ebotcazou at gcc dot gnu.org
2021-10-20 8:46 ` cvs-commit at gcc dot gnu.org
2021-10-20 8:47 ` cvs-commit at gcc dot gnu.org
2021-10-20 8:50 ` ebotcazou at gcc dot gnu.org
2021-10-20 17:58 ` gcc_bugzilla at axeitado dot com
2021-10-20 19:59 ` reiter.christoph at gmail dot com
2022-05-22 15:19 ` reiter.christoph at gmail dot com
2022-05-22 15:49 ` charlet 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-100486-4-uPILr1p41D@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).