Uploaded SLES binaries:
07d289c409e359f1d453d3b3ff66dfa36889d28b
clang+llvm-7.0.0-x86_64-linux-sles11.3.tar.xz
2c07e6f7ebcb71852ad3fe8d69dc7ca3ee580a59
clang+llvm-7.0.0-x86_64-linux-sles12.3.tar.xz
On Mon, Sep 17, 2018 at 6:42 AM Hans Wennborg via Release-testers <
release-test...@lists.llvm.org
A contiguous range certainly can be described with a low_pc/high_pc pair. if
LLDB is looking for DW_AT_ranges but not low/high pairs, it risks missing
information about a CU. I'm not an LLDB dev but I can't imagine anyone
thinking that it would be a problem to fix that.
--paulr
From: sgraen...
Hi Paul, thanks for the clarification. Yes, that was my fault. The LTO object
DWARF has multiple top-level compile unit tags and only the first one has a
DW_AT_ranges attribute.
One more thought here: In DWARFDebugInfo::GetCompileUnitAranges() LLDB
currently tries to read .debug_aranges and if
Are the nested DW_TAG_compile_unit tags in my LTO object missing their
DW_AT_ranges or is that expected?
Compile units should never be nested. That's invalid DWARF. A unit is the root
of the DIE tree described by each unit header.
Whatever is producing one unit contained inside another is doing
Le 17/09/2018 à 13:41, Hans Wennborg via Release-testers a écrit :
> Dear testers,
>
> The final version of 7.0.0 has been tagged from the branch at r342370.
> It is identical to rc3 modulo release notes and docs changes.
>
> Please build the final binaries and upload to the sftp.
>
> For those
On 17 Sep 2018, at 13:41, Hans Wennborg via Release-testers
wrote:
>
> The final version of 7.0.0 has been tagged from the branch at r342370.
> It is identical to rc3 modulo release notes and docs changes.
There weren't any code changes relative to rc3, so nothing changed in the test
results e
