search for: suture

...TADATA_KIND records. The latter is used only in the METADATA_ATTACHMENT block within function blocks (for metadata attached to instructions). For ThinLTO we want to delay the parsing of module level metadata until all functions have been imported from that module (there is some bookkeeping used to suture it up when we read it during a post-pass). However, I do need the METADATA_KIND records since that is used when parsing the function body being imported. In my ThinLTO prototype I was simply skipping the first METADATA_BLOCK and always parsing the second, since I knew from inspecting the BitcodeWri...

...adata on the instructions that were imported, but saves > > the index used by the bitcode reader used to correlate with the > > metadata when it is ready (i.e. the MDValuePtrs index), and skips the > > metadata parsing. During finalization we parse just the metadata, and > > suture it up during metadata value mapping using the saved index. > > AFAICT, the gold-plugin currently does similar work. (Rafael knows > this code better (I've only introduced bugs there), but IIRC he's on > vacation until next week.) Even in "full" LTO. > > Have a...

...kages/samba/netcmd/__init__.py", line 175, in _run return self.run(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/samba/netcmd/dns.py", line 994, in run None, record_type, select_flags, None, None) Thanks, Robb Schiefer Director of Engineering Suture Health, Inc.

...> > File "/usr/lib/python2.7/dist-packages/samba/netcmd/dns.py", line 994, in > run > > None, record_type, select_flags, None, None) > > > > > > > > > > Thanks, > > > > Robb Schiefer > > Director of Engineering > > Suture Health, Inc. > > > -- Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, bâtiment A 12 avenue Jules Verne 44230 Saint Sébastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil.it Samba install wiki for Frenchies : https://dev.tranquil.it WAPT, software deployment made e...

...and metadata. Therefore, the lazy metadata parsing support in BitcodeReader, which parses all the metadata once the first function is materialized, are not applicable. We may instantiate a BitcodeReader multiple times for a module, if multiple functions are eventually imported, and we need a way to suture up the metadata to the functions imported by an earlier BitcodeReader instantiation. The high level summary is that during the initial import we leave the temporary metadata on the instructions that were imported, but save the index used by the bitcode reader used to correlate with the metadata whe...

...gt; > File "/usr/lib/python2.7/dist-packages/samba/netcmd/dns.py", line > 994, in run > > None, record_type, select_flags, None, None) > > > > > > > > > > Thanks, > > > > Robb Schiefer > > Director of Engineering > > Suture Health, Inc. > > > -- Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, bâtiment A 12 avenue Jules Verne 44230 Saint Sébastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil.it Samba install wiki for Frenchies : https://dev.tranquil.it WAPT, software deployment made ea...

...ore, the lazy metadata parsing support in > BitcodeReader, which parses all the metadata once the first function > is materialized, are not applicable. We may instantiate a > BitcodeReader multiple times for a module, if multiple functions are > eventually imported, and we need a way to suture up the metadata to > the functions imported by an earlier BitcodeReader instantiation. The > high level summary is that during the initial import we leave the > temporary metadata on the instructions that were imported, but save > the index used by the bitcode reader used to correlate w...

...tadata parsing support in >> BitcodeReader, which parses all the metadata once the first function >> is materialized, are not applicable. We may instantiate a >> BitcodeReader multiple times for a module, if multiple functions are >> eventually imported, and we need a way to suture up the metadata to >> the functions imported by an earlier BitcodeReader instantiation. The >> high level summary is that during the initial import we leave the >> temporary metadata on the instructions that were imported, but save >> the index used by the bitcode reader use...

...itcodeReader, which parses all the metadata once the first function >>>>> is materialized, are not applicable. We may instantiate a >>>>> BitcodeReader multiple times for a module, if multiple functions are >>>>> eventually imported, and we need a way to suture up the metadata to >>>>> the functions imported by an earlier BitcodeReader instantiation. The >>>>> high level summary is that during the initial import we leave the >>>>> temporary metadata on the instructions that were imported, but save >>>&...

...ta parsing support in > > BitcodeReader, which parses all the metadata once the first function > > is materialized, are not applicable. We may instantiate a > > BitcodeReader multiple times for a module, if multiple functions are > > eventually imported, and we need a way to suture up the metadata to > > the functions imported by an earlier BitcodeReader instantiation. The > > high level summary is that during the initial import we leave the > > temporary metadata on the instructions that were imported, but save > > the index used by the bitcode reader...

...rt in > >> BitcodeReader, which parses all the metadata once the first function > >> is materialized, are not applicable. We may instantiate a > >> BitcodeReader multiple times for a module, if multiple functions are > >> eventually imported, and we need a way to suture up the metadata to > >> the functions imported by an earlier BitcodeReader instantiation. The > >> high level summary is that during the initial import we leave the > >> temporary metadata on the instructions that were imported, but save > >> the index used by th...

...itial import it leaves the temporary metadata on the instructions that were imported, but saves the index used by the bitcode reader used to correlate with the metadata when it is ready (i.e. the MDValuePtrs index), and skips the metadata parsing. During finalization we parse just the metadata, and suture it up during metadata value mapping using the saved index. > >> >> >> b. Import Tuning: >> >> Tuning the import strategy will be an iterative process that will >> continue to be refined over time. It involves several different types >> of changes: addin...

...t;>> BitcodeReader, which parses all the metadata once the first function >>>> is materialized, are not applicable. We may instantiate a >>>> BitcodeReader multiple times for a module, if multiple functions are >>>> eventually imported, and we need a way to suture up the metadata to >>>> the functions imported by an earlier BitcodeReader instantiation. The >>>> high level summary is that during the initial import we leave the >>>> temporary metadata on the instructions that were imported, but save >>>> the inde...

...rt in >> > BitcodeReader, which parses all the metadata once the first function >> > is materialized, are not applicable. We may instantiate a >> > BitcodeReader multiple times for a module, if multiple functions are >> > eventually imported, and we need a way to suture up the metadata to >> > the functions imported by an earlier BitcodeReader instantiation. The >> > high level summary is that during the initial import we leave the >> > temporary metadata on the instructions that were imported, but save >> > the index used by th...

...Reader, which parses all the metadata once the first function > >> >> is materialized, are not applicable. We may instantiate a > >> >> BitcodeReader multiple times for a module, if multiple functions are > >> >> eventually imported, and we need a way to suture up the metadata to > >> >> the functions imported by an earlier BitcodeReader instantiation. The > >> >> high level summary is that during the initial import we leave the > >> >> temporary metadata on the instructions that were imported, but save > &g...

I've included below an RFC for implementing ThinLTO in LLVM, looking forward to feedback and questions. Thanks! Teresa RFC to discuss plans for implementing ThinLTO upstream. Background can be found in slides from EuroLLVM 2015: https://drive.google.com/open?id=0B036uwnWM6RWWER1ZEl5SUNENjQ&authuser=0) As described in the talk, we have a prototype implementation, and would like to