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 bootstrap/98860] [11 Regression] bootstrap failure on MinGW-w64 windows 10 Date: Tue, 23 Mar 2021 14:02:13 +0000 [thread overview] Message-ID: <bug-98860-4-VmZ2wW9YND@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98860-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98860 --- Comment #45 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I have tried the mingw gcc/binutils crosses we have in Fedora (gcc 10.2.1) and get: i686-w64-mingw32-objdump -h ./pr98860.exe ./pr98860.exe: file format pei-i386 Sections: Idx Name Size VMA LMA File off Algn 0 .debug_loclists 0000002a 00000000 00000000 00000448 2**0 CONTENTS, READONLY, DEBUGGING 1 .debug_rnglists 00000013 00000000 00000000 00000648 2**0 CONTENTS, READONLY, DEBUGGING 2 .text 000017d4 00401000 00401000 00000a00 2**4 CONTENTS, ALLOC, LOAD, READONLY, CODE, DATA 3 .data 00000034 00403000 00403000 00002200 2**2 CONTENTS, ALLOC, LOAD, DATA 4 .rdata 000008ec 00404000 00404000 00002400 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 5 .eh_frame 000008d0 00405000 00405000 00002e00 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 6 .bss 00000408 00406000 00406000 00000000 2**5 ALLOC 7 .idata 00000588 00407000 00407000 00003800 2**2 CONTENTS, ALLOC, LOAD, DATA 8 .CRT 00000034 00408000 00408000 00003e00 2**2 CONTENTS, ALLOC, LOAD, DATA 9 .tls 00000008 00409000 00409000 00004000 2**2 CONTENTS, ALLOC, LOAD, DATA 10 .debug_aranges 00000078 0040a000 0040a000 00004200 2**3 CONTENTS, READONLY, DEBUGGING 11 .debug_info 00003530 0040b000 0040b000 00004400 2**0 CONTENTS, READONLY, DEBUGGING 12 .debug_abbrev 0000063e 0040f000 0040f000 00007a00 2**0 CONTENTS, READONLY, DEBUGGING 13 .debug_line 00000795 00410000 00410000 00008200 2**0 CONTENTS, READONLY, DEBUGGING 14 .debug_frame 00000038 00411000 00411000 00008a00 2**2 CONTENTS, READONLY, DEBUGGING 15 .debug_str 00000360 00412000 00412000 00008c00 2**0 CONTENTS, READONLY, DEBUGGING 16 .debug_loc 0000039d 00413000 00413000 00009000 2**0 CONTENTS, READONLY, DEBUGGING 17 .debug_ranges 000000d8 00414000 00414000 00009400 2**0 CONTENTS, READONLY, DEBUGGING so in that case it seems that .debug_{loclists,rnglists} etc. should use non-zero VMA/LMA like other debug sections rather than zero like they currently do.
next prev parent reply other threads:[~2021-03-23 14:02 UTC|newest] Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-27 22:20 [Bug bootstrap/98860] New: boostrap " unlvsur at live dot com 2021-01-27 23:10 ` [Bug bootstrap/98860] " unlvsur at live dot com 2021-01-28 0:34 ` unlvsur at live dot com 2021-01-28 0:49 ` unlvsur at live dot com 2021-01-28 2:35 ` unlvsur at live dot com 2021-01-28 2:40 ` unlvsur at live dot com 2021-01-28 7:39 ` unlvsur at live dot com 2021-01-28 7:41 ` [Bug bootstrap/98860] [11 Regression] " rguenth at gcc dot gnu.org 2021-01-28 8:04 ` unlvsur at live dot com 2021-01-28 8:48 ` unlvsur at live dot com 2021-01-28 9:25 ` unlvsur at live dot com 2021-01-28 9:31 ` jakub at gcc dot gnu.org 2021-01-28 9:32 ` unlvsur at live dot com 2021-01-28 9:36 ` jakub at gcc dot gnu.org 2021-01-28 9:38 ` unlvsur at live dot com 2021-01-28 9:40 ` unlvsur at live dot com 2021-01-28 9:49 ` lh_mouse at 126 dot com 2021-01-28 14:32 ` unlvsur at live dot com 2021-01-28 14:35 ` jakub at gcc dot gnu.org 2021-01-28 15:36 ` unlvsur at live dot com 2021-01-28 15:48 ` unlvsur at live dot com 2021-01-29 3:44 ` lh_mouse at 126 dot com 2021-02-02 12:05 ` ebotcazou at gcc dot gnu.org 2021-02-03 12:56 ` nix at esperi dot org.uk 2021-02-03 15:27 ` nix at esperi dot org.uk 2021-02-03 15:29 ` nix at esperi dot org.uk 2021-02-06 22:08 ` mikpelinux at gmail dot com 2021-02-06 22:14 ` unlvsur at live dot com 2021-02-07 9:19 ` brechtsanders at users dot sourceforge.net 2021-02-07 17:08 ` mikpelinux at gmail dot com 2021-02-07 20:38 ` unlvsur at live dot com 2021-02-08 21:45 ` mikpelinux at gmail dot com 2021-02-09 20:22 ` mikpelinux at gmail dot com 2021-02-09 20:38 ` redi at gcc dot gnu.org 2021-02-09 20:39 ` redi at gcc dot gnu.org 2021-02-16 14:30 ` hjl.tools at gmail dot com 2021-02-26 12:38 ` rguenth at gcc dot gnu.org 2021-02-26 12:48 ` ssbssa at yahoo dot de 2021-02-26 17:55 ` jakub at gcc dot gnu.org 2021-03-01 22:05 ` [Bug bootstrap/98860] [11 Regression] bootstrap " mikpelinux at gmail dot com 2021-03-17 10:42 ` jakub at gcc dot gnu.org 2021-03-17 12:03 ` jyong at gcc dot gnu.org 2021-03-17 12:39 ` jakub at gcc dot gnu.org 2021-03-17 13:05 ` jakub at gcc dot gnu.org 2021-03-18 14:26 ` jyong at gcc dot gnu.org 2021-03-18 14:42 ` jakub at gcc dot gnu.org 2021-03-23 14:02 ` jakub at gcc dot gnu.org [this message] 2021-03-23 14:54 ` jyong at gcc dot gnu.org 2021-03-23 15:09 ` jakub at gcc dot gnu.org 2021-03-23 15:43 ` jyong at gcc dot gnu.org 2021-03-23 16:02 ` jakub at gcc dot gnu.org 2021-03-23 16:12 ` jyong at gcc dot gnu.org 2021-03-23 17:12 ` jyong at gcc dot gnu.org 2021-03-23 17:59 ` jyong at gcc dot gnu.org 2021-03-23 18:16 ` jakub at gcc dot gnu.org 2021-03-23 18:26 ` jakub at gcc dot gnu.org 2021-03-23 18:26 ` jakub at gcc dot gnu.org 2021-03-24 13:44 ` jyong at gcc dot gnu.org 2021-03-24 19:31 ` rogero at howzatt dot co.uk 2021-03-31 7:12 ` cvs-commit at gcc dot gnu.org 2021-03-31 7:13 ` jakub at gcc dot gnu.org 2021-03-31 13:42 ` jyong 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-98860-4-VmZ2wW9YND@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).