From: Andi Kleen <ak@linux.intel.com> To: Linus Torvalds <torvalds@linux-foundation.org> Cc: Fengguang Wu <fengguang.wu@intel.com>, Jeff Kirsher <jeffrey.t.kirsher@intel.com>, Network Development <netdev@vger.kernel.org>, "David S. Miller" <davem@davemloft.net>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, intel-wired-lan@lists.osuosl.org, Michal Marek <mmarek@suse.cz>, Sam Ravnborg <sam@ravnborg.org>, Dirk Gouders <dirk@gouders.net>, Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>, kbuild test robot <lkp@intel.com>, "Zhang, Rui" <rui.zhang@intel.com>, "Lu, Aaron" <aaron.lu@intel.com>, "H.J. Lu" <hjl.tools@gmail.com> Subject: Re: CONFIG_DEBUG_INFO_SPLIT impacts on faddr2line Date: Mon, 13 Nov 2017 15:51:40 -0800 [thread overview] Message-ID: <20171113235140.GR8522@tassilo.jf.intel.com> (raw) In-Reply-To: <CA+55aFzEb1qp872nO4Y20cY9WHdek2MC=7XX1xNcN8q1WvTOaw@mail.gmail.com> > I wonder if there is some way to use the split format for the > intermediate files, but then for the very final link bring them all in > and make the end result be a traditional single binary. I'm not > talking the separate "dwp" package that packs multiple dwo files into > one, but to actually link them all in at the one. > > Sure, it would lose some of the advantage, but I think a large portion > of the -gsplit-dwarf advantage is about the intermediate state. No? Not sure it's worth to do complicated workarounds. I assume it will be not that difficult to fix binutils (after all gdb works), and disabling the option is a reasonable workaround. > > I tried to google for it, but couldn't find anything. But apparently > elfutils doesn't support dwo files either. It seems mainly the linker > and gdb itself that supports it. The original design document is https://gcc.gnu.org/wiki/DebugFission -Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <ak@linux.intel.com> To: intel-wired-lan@osuosl.org Subject: [Intel-wired-lan] CONFIG_DEBUG_INFO_SPLIT impacts on faddr2line Date: Mon, 13 Nov 2017 15:51:40 -0800 [thread overview] Message-ID: <20171113235140.GR8522@tassilo.jf.intel.com> (raw) In-Reply-To: <CA+55aFzEb1qp872nO4Y20cY9WHdek2MC=7XX1xNcN8q1WvTOaw@mail.gmail.com> > I wonder if there is some way to use the split format for the > intermediate files, but then for the very final link bring them all in > and make the end result be a traditional single binary. I'm not > talking the separate "dwp" package that packs multiple dwo files into > one, but to actually link them all in at the one. > > Sure, it would lose some of the advantage, but I think a large portion > of the -gsplit-dwarf advantage is about the intermediate state. No? Not sure it's worth to do complicated workarounds. I assume it will be not that difficult to fix binutils (after all gdb works), and disabling the option is a reasonable workaround. > > I tried to google for it, but couldn't find anything. But apparently > elfutils doesn't support dwo files either. It seems mainly the linker > and gdb itself that supports it. The original design document is https://gcc.gnu.org/wiki/DebugFission -Andi
next prev parent reply other threads:[~2017-11-13 23:51 UTC|newest] Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-11-07 10:21 [vlan_device_event] BUG: unable to handle kernel paging request at 6b6b6ccf Fengguang Wu 2017-11-07 16:25 ` Linus Torvalds 2017-11-07 16:46 ` Fengguang Wu 2017-11-08 9:48 ` Fengguang Wu 2017-11-08 16:20 ` Linus Torvalds 2017-11-08 16:20 ` [Intel-wired-lan] " Linus Torvalds 2017-11-08 17:12 ` Fengguang Wu 2017-11-08 17:12 ` [Intel-wired-lan] " Fengguang Wu 2017-11-08 17:18 ` Fengguang Wu 2017-11-08 17:18 ` [Intel-wired-lan] " Fengguang Wu 2017-11-08 18:05 ` Linus Torvalds 2017-11-08 18:05 ` [Intel-wired-lan] " Linus Torvalds 2017-11-08 18:36 ` Alexander Duyck 2017-11-08 18:36 ` [Intel-wired-lan] " Alexander Duyck 2017-11-09 3:12 ` Fengguang Wu 2017-11-09 3:12 ` [Intel-wired-lan] " Fengguang Wu 2017-11-09 4:09 ` Fengguang Wu 2017-11-09 4:09 ` [Intel-wired-lan] " Fengguang Wu 2017-11-09 7:22 ` Fengguang Wu 2017-11-09 7:22 ` [Intel-wired-lan] " Fengguang Wu 2017-11-09 6:34 ` Cong Wang 2017-11-09 6:34 ` [Intel-wired-lan] " Cong Wang 2017-11-09 6:55 ` Fengguang Wu 2017-11-09 6:55 ` [Intel-wired-lan] " Fengguang Wu 2017-11-09 7:43 ` Fengguang Wu 2017-11-09 7:43 ` [Intel-wired-lan] " Fengguang Wu 2017-11-09 15:51 ` Girish Moodalbail 2017-11-09 15:51 ` [Intel-wired-lan] " Girish Moodalbail 2017-11-10 0:16 ` Cong Wang 2017-11-10 0:16 ` [Intel-wired-lan] " Cong Wang 2017-11-12 19:31 ` Linus Torvalds 2017-11-12 19:31 ` [Intel-wired-lan] " Linus Torvalds 2017-11-13 1:13 ` CONFIG_DEBUG_INFO_SPLIT impacts on faddr2line Fengguang Wu 2017-11-13 1:13 ` [Intel-wired-lan] " Fengguang Wu 2017-11-13 2:05 ` Zhang Rui 2017-11-13 2:05 ` [Intel-wired-lan] " Zhang Rui 2017-11-13 2:22 ` Fengguang Wu 2017-11-13 2:22 ` [Intel-wired-lan] " Fengguang Wu 2017-11-13 18:52 ` Andi Kleen 2017-11-13 18:52 ` [Intel-wired-lan] " Andi Kleen 2017-11-13 19:14 ` Linus Torvalds 2017-11-13 19:14 ` [Intel-wired-lan] " Linus Torvalds 2017-11-13 20:10 ` Andi Kleen 2017-11-13 20:10 ` [Intel-wired-lan] " Andi Kleen 2017-11-13 20:14 ` H.J. Lu 2017-11-13 20:14 ` [Intel-wired-lan] " H.J. Lu 2017-11-13 20:56 ` Linus Torvalds 2017-11-13 20:56 ` [Intel-wired-lan] " Linus Torvalds 2017-11-13 21:41 ` Andi Kleen 2017-11-13 21:41 ` [Intel-wired-lan] " Andi Kleen 2017-11-13 21:57 ` Linus Torvalds 2017-11-13 21:57 ` [Intel-wired-lan] " Linus Torvalds 2017-11-13 23:51 ` Andi Kleen [this message] 2017-11-13 23:51 ` Andi Kleen 2017-11-14 8:13 ` Fengguang Wu 2017-11-14 8:13 ` [Intel-wired-lan] " Fengguang Wu 2017-11-09 2:43 ` [vlan_device_event] BUG: unable to handle kernel paging request at 6b6b6ccf Fengguang Wu 2017-11-09 6:48 ` Fengguang Wu
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=20171113235140.GR8522@tassilo.jf.intel.com \ --to=ak@linux.intel.com \ --cc=aaron.lu@intel.com \ --cc=davem@davemloft.net \ --cc=dirk@gouders.net \ --cc=fengguang.wu@intel.com \ --cc=hjl.tools@gmail.com \ --cc=intel-wired-lan@lists.osuosl.org \ --cc=jeffrey.t.kirsher@intel.com \ --cc=linux-kbuild@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=lkp@intel.com \ --cc=mmarek@suse.cz \ --cc=netdev@vger.kernel.org \ --cc=rui.zhang@intel.com \ --cc=sam@ravnborg.org \ --cc=torvalds@linux-foundation.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 an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.