Displaying 7 results from an estimated 7 matches for "rangelist".
2017 Apr 15
2
About TableGen RangeList
Hi All,
One thing I believe also bothers someone else. Say we have the following
code snippet:
bits<32> insnEncoding;
let insnEncoding{15-12} = 0b0100;
Can we write the let expression with range list like this, with the same
meaning?
let insnEncoding{12-15} = 0b0100;
I take a look on TGParser::ParseRangePiece (lib/TableGen/TGParser.cpp),
seems the
answer is YES. Can anyone
2017 Apr 16
3
About TableGen RangeList
On 15 April 2017 at 19:52, 陳韋任 via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> Okay, a little experiment shows the order matters.
Interesting, thanks for reporting back. Personally I find it pretty
scary that we support the second form at all. It's mixing two
different endiannesses with no real indication of which one will win.
Tim.
2020 Nov 09
1
Fragmented DWARF
...ta;
FrameData.substr(EntryOffset, InitialLength + 4)
...
InputSec = Dwarf.getDWARFObj().getLocSection();
InputSec.Data.substr(Offset, Length);
...
DWARFDataExtractor RangesData(Context.getDWARFObj(), *RangeSection,
isLittleEndian, getAddressByteSize());
uint64_t ActualRangeListOffset = RangeSectionBase + RangeListOffset;
RangeList.extract(RangesData, &ActualRangeListOffset);
i.e. It is possible to access random piece of DWARFSection.
If object::ObjectFile would contain fragmented sections then
we need a solution of how that could work.
One possibility is to create...
2020 Nov 05
3
Fragmented DWARF
Hi James,
On 05.11.2020 17:59, James Henderson wrote:
> (Resending with history trimmed to avoid it getting stuck in moderator
> queue).
>
> Hi Alexey,
>
> Just an update - I identified the cause of the "Generated debug info
> is broken" error message when I tried to build things locally: the
> `outStreamer` instance is initialised with the host Triple,
2020 Jun 04
4
[Debuginfo][DWARF][LLD] Remove obsolete debug info in lld.
...et, so slicing and dicing them is
cheap.
But the tombstone problem still exists for the CU's debug_ranges -
though /maybe/ it could be carefully constructed from fragments...
that's going to be a /lot/ of sections in the end though.
> .debug_aranges is functionally equivalent to the CU rangelist.
Yup. (as we've touched on before, we don't use aranges at Google -
instead relying on CU's ranges which are just a little more expensive
to retrieve - but no need to duplicate the data in both places - if
consumers really find the aranges worthwhile to avoid parsing a few
attributes o...
2020 Jun 03
2
[Debuginfo][DWARF][LLD] Remove obsolete debug info in lld.
On Wed, Jun 3, 2020 at 6:34 AM Robinson, Paul <paul.robinson at sony.com> wrote:
>
> DWARF was designed in an era when COMDAT and ICF were not a thing, or at least not common, certainly not when talking about function code. The overhead of a unit occurred only once per translation unit, so that expense was reasonably amortized.
>
>
>
> Splitting functions into their own
2020 Jun 09
2
[Debuginfo][DWARF][LLD] Remove obsolete debug info in lld.
...t; But the tombstone problem still exists for the CU's debug_ranges -
> > though /maybe/ it could be carefully constructed from fragments...
> > that's going to be a /lot/ of sections in the end though.
> >
> > > .debug_aranges is functionally equivalent to the CU rangelist.
> >
> > Yup. (as we've touched on before, we don't use aranges at Google -
> > instead relying on CU's ranges which are just a little more expensive
> > to retrieve - but no need to duplicate the data in both places - if
> > consumers really find the arang...