search for: diblob

...will we handle references in DWARF2 or global relocations for >>>> non-type template parameters? >>>> * We can use a “relocation” metadata as part of the format. >>>> * Representable as a tuple that has the DIType and the offset within >>>> the DIBlob as where to write the final relocation/offset for the reference >>>> at emission time. >>>> >>>> Why break up the types at all? >>>> * To enable non-debug format aware linking and type uniquing for LTO >>>> that won’t be huge in size. W...

...>>> How will we handle references in DWARF2 or global relocations for >>> non-type template parameters? >>> * We can use a “relocation” metadata as part of the format. >>> * Representable as a tuple that has the DIType and the offset within >>> the DIBlob as where to write the final relocation/offset for the reference >>> at emission time. >>> >>> Why break up the types at all? >>> * To enable non-debug format aware linking and type uniquing for LTO >>> that won’t be huge in size. We break up the types...

...See below) >> >> How will we handle references in DWARF2 or global relocations for >> non-type template parameters? >> * We can use a “relocation” metadata as part of the format. >> * Representable as a tuple that has the DIType and the offset within >> the DIBlob as where to write the final relocation/offset for the reference >> at emission time. >> >> Why break up the types at all? >> * To enable non-debug format aware linking and type uniquing for LTO >> that won’t be huge in size. We break up the types so we don’t need to...

...references in DWARF2 or global relocations for >>>>> non-type template parameters? >>>>> * We can use a “relocation” metadata as part of the format. >>>>> * Representable as a tuple that has the DIType and the offset >>>>> within the DIBlob as where to write the final relocation/offset for the >>>>> reference at emission time. >>>>> >>>>> Why break up the types at all? >>>>> * To enable non-debug format aware linking and type uniquing for >>>>> LTO that won’...

...le relocations for the offsets. (See below) > > How will we handle references in DWARF2 or global relocations for non-type template parameters? > * We can use a “relocation” metadata as part of the format. > * Representable as a tuple that has the DIType and the offset within the DIBlob as where to write the final relocation/offset for the reference at emission time. > > Why break up the types at all? > * To enable non-debug format aware linking and type uniquing for LTO that won’t be huge in size. We break up the types so we don’t need to parse debug information to l...

...tions for the offsets. (See below) > > How will we handle references in DWARF2 or global relocations for non-type > template parameters? > * We can use a “relocation” metadata as part of the format. > * Representable as a tuple that has the DIType and the offset within > the DIBlob as where to write the final relocation/offset for the reference > at emission time. > > Why break up the types at all? > * To enable non-debug format aware linking and type uniquing for LTO > that won’t be huge in size. We break up the types so we don’t need to parse > debug in...

...references and module relocations for the offsets. (See below) How will we handle references in DWARF2 or global relocations for non-type template parameters? * We can use a “relocation” metadata as part of the format. * Representable as a tuple that has the DIType and the offset within the DIBlob as where to write the final relocation/offset for the reference at emission time. Why break up the types at all? * To enable non-debug format aware linking and type uniquing for LTO that won’t be huge in size. We break up the types so we don’t need to parse debug information to link two modules...

...references and module relocations for the offsets. (See below) How will we handle references in DWARF2 or global relocations for non-type template parameters? * We can use a “relocation” metadata as part of the format. * Representable as a tuple that has the DIType and the offset within the DIBlob as where to write the final relocation/offset for the reference at emission time. Why break up the types at all? * To enable non-debug format aware linking and type uniquing for LTO that won’t be huge in size. We break up the types so we don’t need to parse debug information to link two modules...

...s. (See below) > > > > How will we handle references in DWARF2 or global relocations for non-type > template parameters? > > * We can use a “relocation” metadata as part of the format. > > * Representable as a tuple that has the DIType and the offset within > the DIBlob as where to write the final relocation/offset for the reference > at emission time. > > > > Why break up the types at all? > > * To enable non-debug format aware linking and type uniquing for LTO > that won’t be huge in size. We break up the types so we don’t need to pars...

...; >> How will we handle references in DWARF2 or global relocations for >> non-type template parameters? >> >> * We can use a “relocation” metadata as part of the format. >> >> * Representable as a tuple that has the DIType and the offset within >> the DIBlob as where to write the final relocation/offset for the reference >> at emission time. >> >> >> >> Why break up the types at all? >> >> * To enable non-debug format aware linking and type uniquing for LTO >> that won’t be huge in size. We break up th...

...fsets. (See below) > > > > How will we handle references in DWARF2 or global relocations for non-type template parameters? > > * We can use a “relocation” metadata as part of the format. > > * Representable as a tuple that has the DIType and the offset within the DIBlob as where to write the final relocation/offset for the reference at emission time. > > > > Why break up the types at all? > > * To enable non-debug format aware linking and type uniquing for LTO that won’t be huge in size. We break up the types so we don’t need to parse deb...

...See below) >> >> How will we handle references in DWARF2 or global relocations for >> non-type template parameters? >> * We can use a “relocation” metadata as part of the format. >> * Representable as a tuple that has the DIType and the offset within >> the DIBlob as where to write the final relocation/offset for the reference >> at emission time. >> >> Why break up the types at all? >> * To enable non-debug format aware linking and type uniquing for LTO >> that won’t be huge in size. We break up the types so we don’t need to...

...>>> How will we handle references in DWARF2 or global relocations for non-type template parameters? >>> >>> * We can use a “relocation” metadata as part of the format. >>> >>> * Representable as a tuple that has the DIType and the offset within the DIBlob as where to write the final relocation/offset for the reference at emission time. >>> >>> >>> >>> Why break up the types at all? >>> >>> * To enable non-debug format aware linking and type uniquing for LTO that won’t be huge in size. We break...

...references and module relocations for the offsets. (See below) How will we handle references in DWARF2 or global relocations for non-type template parameters? * We can use a “relocation” metadata as part of the format. * Representable as a tuple that has the DIType and the offset within the DIBlob as where to write the final relocation/offset for the reference at emission time. Why break up the types at all? * To enable non-debug format aware linking and type uniquing for LTO that won’t be huge in size. We break up the types so we don’t need to parse debug information to link two modules...

...;> >> >> How will we handle references in DWARF2 or global relocations for non-type template parameters? >> >> * We can use a “relocation” metadata as part of the format. >> >> * Representable as a tuple that has the DIType and the offset within the DIBlob as where to write the final relocation/offset for the reference at emission time. >> >> >> >> Why break up the types at all? >> >> * To enable non-debug format aware linking and type uniquing for LTO that won’t be huge in size. We break up the types so we...

...e relocations for the offsets. (See below) > > How will we handle references in DWARF2 or global relocations for non-type template parameters? > * We can use a “relocation” metadata as part of the format. > * Representable as a tuple that has the DIType and the offset within the DIBlob as where to write the final relocation/offset for the reference at emission time. > > Why break up the types at all? > * To enable non-debug format aware linking and type uniquing for LTO that won’t be huge in size. We break up the types so we don’t need to parse debug information to...

...s. (See below) > > > > How will we handle references in DWARF2 or global relocations for non-type > template parameters? > > * We can use a “relocation” metadata as part of the format. > > * Representable as a tuple that has the DIType and the offset within > the DIBlob as where to write the final relocation/offset for the reference > at emission time. > > > > Why break up the types at all? > > * To enable non-debug format aware linking and type uniquing for LTO > that won’t be huge in size. We break up the types so we don’t need to pars...

...or the offsets. (See below) >> >> How will we handle references in DWARF2 or global relocations for non-type template parameters? >> * We can use a “relocation” metadata as part of the format. >> * Representable as a tuple that has the DIType and the offset within the DIBlob as where to write the final relocation/offset for the reference at emission time. >> >> Why break up the types at all? >> * To enable non-debug format aware linking and type uniquing for LTO that won’t be huge in size. We break up the types so we don’t need to parse debug info...