public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/41405] [4.5 Regression] Bootstrap fails at revision 151873 on *-apple-darwin9 Date: Sun, 20 Sep 2009 15:24:00 -0000 [thread overview] Message-ID: <20090920152422.30015.qmail@sourceware.org> (raw) In-Reply-To: <bug-41405-12313@http.gcc.gnu.org/bugzilla/> ------- Comment #13 from dominiq at lps dot ens dot fr 2009-09-20 15:24 ------- The culprit is indeed r151815. Reverting the change after having updated to r151893 on i686-apple-darwin9 ( r151895 on powerpc-apple-darwin9) allows a successful bootstrap (currently building the libs on powerpc). In http://gcc.gnu.org/ml/gcc-patches/2009-09/msg00220.html the patch is motivated by: > I think the important question is whether older debuggers would be able > to deal gracefully with these location entries or constant values. I > understand they're supposed to, and I have no evidence that GDB isn't, so > I offer this patch to revert the last-minute addition of tests for > dwarf_version >= 4 in the VTA merge patch. > > Should I check it in so that we can get a better idea of what, if > anything, breaks? Apparently the changes affect more than GDB. So now that you have "get a better idea of what, if anything, breaks" it seems appropriate to revert them. > Yes, probably the apple tools barf on the new dwarf opcodes. Please report the > issue to them. As far as I understand the problem, I do not see why tools not designed to accept "dwarf_version 4" can be blamed for that (it would be like blaming the CD player in my car for not reading MP3 CDs). > A GCC side fix would be to add an option to restrict dwarf to dwarf2 and turn that option on by > default for darwin. What is the difference with reverting the patch? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41405
next prev parent reply other threads:[~2009-09-20 15:24 UTC|newest] Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-09-19 9:49 [Bug bootstrap/41405] New: " dominiq at lps dot ens dot fr 2009-09-19 19:56 ` [Bug bootstrap/41405] " rguenth at gcc dot gnu dot org 2009-09-19 20:44 ` rguenth at gcc dot gnu dot org 2009-09-19 21:31 ` dominiq at lps dot ens dot fr 2009-09-19 21:40 ` dominiq at lps dot ens dot fr 2009-09-19 22:04 ` rguenth at gcc dot gnu dot org 2009-09-19 23:14 ` howarth at nitro dot med dot uc dot edu 2009-09-19 23:22 ` howarth at nitro dot med dot uc dot edu 2009-09-19 23:23 ` howarth at nitro dot med dot uc dot edu 2009-09-19 23:24 ` howarth at nitro dot med dot uc dot edu 2009-09-19 23:26 ` howarth at nitro dot med dot uc dot edu 2009-09-19 23:37 ` howarth at nitro dot med dot uc dot edu 2009-09-20 8:01 ` developer at sandoe-acoustics dot co dot uk 2009-09-20 9:39 ` developer at sandoe-acoustics dot co dot uk 2009-09-20 15:24 ` dominiq at lps dot ens dot fr [this message] 2009-09-20 16:23 ` howarth at nitro dot med dot uc dot edu 2009-09-20 16:24 ` howarth at nitro dot med dot uc dot edu 2009-09-20 16:37 ` rguenth at gcc dot gnu dot org 2009-09-20 17:02 ` howarth at nitro dot med dot uc dot edu 2009-09-20 21:49 ` pogma at gcc dot gnu dot org 2009-09-20 22:38 ` developer at sandoe-acoustics dot co dot uk 2009-09-21 7:01 ` jakub at gcc dot gnu dot org 2009-09-21 8:05 ` [Bug bootstrap/41405] [4.5 Regression] Bootstrap fails on *-apple-darwin* due to revision 151815 dominiq at lps dot ens dot fr 2009-09-21 9:04 ` developer at sandoe-acoustics dot co dot uk 2009-09-21 10:22 ` jakub at gcc dot gnu dot org 2009-09-21 12:19 ` dominiq at lps dot ens dot fr 2009-09-21 12:45 ` developer at sandoe-acoustics dot co dot uk 2009-09-21 14:25 ` developer at sandoe-acoustics dot co dot uk 2009-09-21 15:37 ` jakub at gcc dot gnu dot org 2009-09-21 16:46 ` developer at sandoe-acoustics dot co dot uk 2009-09-21 17:07 ` howarth at nitro dot med dot uc dot edu 2009-09-21 17:25 ` jakub at gcc dot gnu dot org 2009-09-21 18:50 ` developer at sandoe-acoustics dot co dot uk 2009-09-22 7:08 ` jakub at gcc dot gnu dot org 2009-09-22 13:22 ` jakub at gcc dot gnu dot org 2009-09-22 14:36 ` developer at sandoe-acoustics dot co dot uk 2009-09-22 15:01 ` rguenth at gcc dot gnu dot org 2009-09-22 15:04 ` jakub at gcc dot gnu dot org 2009-09-22 16:09 ` developer at sandoe-acoustics dot co dot uk 2009-09-22 16:38 ` developer at sandoe-acoustics dot co dot uk 2009-09-22 20:17 ` developer at sandoe-acoustics dot co dot uk 2009-09-22 20:47 ` howarth at nitro dot med dot uc dot edu 2009-09-22 21:00 ` dominiq at lps dot ens dot fr 2009-09-22 21:34 ` jakub at gcc dot gnu dot org 2009-09-22 21:42 ` developer at sandoe-acoustics dot co dot uk 2009-09-23 0:11 ` howarth at nitro dot med dot uc dot edu 2009-09-23 1:35 ` howarth at nitro dot med dot uc dot edu 2009-09-23 3:33 ` howarth at nitro dot med dot uc dot edu 2009-09-23 4:22 ` howarth at nitro dot med dot uc dot edu 2009-09-23 9:13 ` developer at sandoe-acoustics dot co dot uk 2009-09-23 9:29 ` dominiq at lps dot ens dot fr 2009-09-23 13:38 ` howarth at nitro dot med dot uc dot edu 2009-09-23 13:49 ` howarth at nitro dot med dot uc dot edu 2009-09-23 13:58 ` developer at sandoe-acoustics dot co dot uk 2009-09-23 14:26 ` howarth at nitro dot med dot uc dot edu 2009-09-23 14:30 ` jakub at gcc dot gnu dot org 2009-09-23 14:53 ` jakub at gcc dot gnu dot org 2009-09-23 15:23 ` howarth at nitro dot med dot uc dot edu 2009-09-23 15:43 ` howarth at nitro dot med dot uc dot edu 2009-09-23 19:40 ` developer at sandoe-acoustics dot co dot uk 2009-09-23 23:06 ` howarth at nitro dot med dot uc dot edu 2009-09-23 23:34 ` howarth at nitro dot med dot uc dot edu 2009-09-24 9:06 ` dominiq at lps dot ens dot fr 2009-09-24 9:40 ` dominiq at lps dot ens dot fr 2009-09-24 13:47 ` howarth at nitro dot med dot uc dot edu 2009-09-24 17:03 ` rth at gcc dot gnu dot org 2009-09-25 8:11 ` developer at sandoe-acoustics dot co dot uk 2009-09-25 14:04 ` howarth at nitro dot med dot uc dot edu 2009-09-25 21:40 ` dominiq at lps dot ens dot fr
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=20090920152422.30015.qmail@sourceware.org \ --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).