Date: Fri, 25 Aug 2017 12:30:11 -0600 From: Warner Losh <imp@bsdimp.com> To: Ed Maste <emaste@freebsd.org> Cc: Ryan Libby <rlibby@gmail.com>, "svn-src-head@freebsd.org" <svn-src-head@freebsd.org>, "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>, src-committers <src-committers@freebsd.org>, John Baldwin <jhb@freebsd.org>, "freebsd-toolchain@freebsd.org" <freebsd-toolchain@freebsd.org> Subject: Re: svn commit: r322824 - in head: lib/clang share/mk usr.bin/clang Message-ID: <CANCZdfqfR_KN0j2-7eJ8J0PAAQHajcEEX=z4V%2BDPgMz-kjCS4g@mail.gmail.com> In-Reply-To: <CAPyFy2AQRVQu-HBGtBDTU0OnmYhcBKMg9OX-vaGVpfA%2B=v-Grw@mail.gmail.com> References: <201708232330.v7NNUPpV052276@repo.freebsd.org> <CAHgpiFwzK5FyB6GDSXdGReO=wAQOAFDxqtQRNZWSR4WHz4ULEA@mail.gmail.com> <CAPyFy2AQRVQu-HBGtBDTU0OnmYhcBKMg9OX-vaGVpfA%2B=v-Grw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 25, 2017 at 12:27 PM, Ed Maste <emaste@freebsd.org> wrote: > On 25 August 2017 at 14:07, Ryan Libby <rlibby@gmail.com> wrote: > > On Wed, Aug 23, 2017 at 4:30 PM, John Baldwin <jhb@freebsd.org> wrote: > >> Author: jhb > >> Date: Wed Aug 23 23:30:25 2017 > >> New Revision: 322824 > >> URL: https://svnweb.freebsd.org/changeset/base/322824 > >> > >> Log: > >> Improve the coverage of debug symbols for MK_DEBUG_FILES. > >> > ... > > This causes llvm to emit hundreds of new warnings [1] for > > "DWARF2 only supports one section per compilation unit" > > > > Are these expected? Are they a concern? Should we silence them? > > Is this an upstream llvm bug [2]? > > I'm not sure they were "expected" but I guess are an unsurprising > consequence of building more things with debug. In any case they're > not a concern. > > It is an llvm bug (the warning really ought not be emitted for empty > sections), but upstream is probably not too concerned as (most? all) > other platforms are not using dwarf2. > > The right answer for us is likely to just stop defaulting to dwarf2 > (and specifying it via CFLAGS for kernel if necessary). > What's the status of kicking gdb out of the tree? If we kick it out, we can stop doing dwarf2 and move to something more modern. Last time this issue came up, that was the decision, pending a few issues with the gdb port which I think John Baldwin is getting close to reaching closure on. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqfR_KN0j2-7eJ8J0PAAQHajcEEX=z4V%2BDPgMz-kjCS4g>