[cfe-dev] DWARFv5 by default in clang?

[David Blaikie via cfe-dev]

Well, made the switch to DWARFv5 by default
in d3b26dea16108c427b19b5480c9edc76edf8f5b4 and included a change to keep
DWARFv4 as the default for linux-androideabi (at least I think I made that
change in the right place). If it needs to be more generic (apply to
non-linux toolchains, but I don't think so?) or can be removed because
Android's OK with DWARFv5 - should be simple to make that change.

On Sun, Jan 23, 2022 at 8:08 PM David Blaikie <dblaikie at gmail.com> wrote:

> Hey Stephen,
>
> I see you added a test to ensure Android uses DWARFv4 here:
> https://reviews.llvm.org/D60238
>
> Is that still the case? I can figure out how to ensure that's the case as
> we transition the default to DWARFv5 for platforms that haven't opted out.
>
> On Tue, Nov 30, 2021 at 9:28 AM Khem Raj <raj.khem at gmail.com> wrote:
>
>> On Tue, Nov 30, 2021 at 9:10 AM via cfe-dev <cfe-dev at lists.llvm.org>
>> wrote:
>> >
>> > > Generic_GCC has many (indirect) derived classes
>> > > (FreeBSD/OpenBSD/Solaris) which override the base
>> > > GetDefaultDwarfVersion().
>> > > The Generic_GCC change will affect
>> > > Haiku/Hurd/Linux/NetBSD/PS4CPU/etc. I have CC'd these folks: if
>> > > your platform is not ready for DWARF v5, you can override
>> > > GetDefaultDwarfVersion() in your toolchain.
>>
>> We have been using v5 in yocto with clang13 onwards as well [1] and
>> have not seen any blockers.
>>
>> [1]
>> https://github.com/kraj/meta-clang/blob/master/recipes-devtools/clang/clang/0027-clang-Switch-defaults-to-dwarf-5-debug-info-on-Linux.patch
>>
>> >
>> > PS4 updated to set v4 explicitly as of
>> >
>> https://github.com/llvm/llvm-project/commit/b8e03be88dc87303f7401ea7b9906947ac67a6db
>> > --paulr
>> > _______________________________________________
>> > cfe-dev mailing list
>> > cfe-dev at lists.llvm.org
>> > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20220123/65662a4f/attachment.html>