search for: 649mb

Hi All, In LTO, we load in the source modules and link the source modules into a destination module. Lots of MDNodes are only used by the source modules, for example Xalan used 649MB for MDNodes after loading and linking, but the actual destination module only has 393MB of MDNodes. There are 649-393MB (40% of 649MB) not used. MDNodes belong to the Context, deleting modules will not release the MDNodes. One possible solution is: In LLVMContext, add “removeUnusedMDNodes"...

On Tue, Nov 12, 2013 at 4:29 PM, Manman Ren <manman.ren at gmail.com> wrote: > Hi All, > > In LTO, we load in the source modules and link the source modules into a > destination module. > Lots of MDNodes are only used by the source modules, for example Xalan > used 649MB for MDNodes after loading and linking, but the actual > destination module only has 393MB of MDNodes. There are 649-393MB (40% of > 649MB) not used. > > MDNodes belong to the Context, deleting modules will not release the > MDNodes. > > One possible solution is: > > In LL...

...at 4:29 PM, Manman Ren <manman.ren at gmail.com> wrote: > >> Hi All, >> >> In LTO, we load in the source modules and link the source modules into a >> destination module. >> Lots of MDNodes are only used by the source modules, for example Xalan >> used 649MB for MDNodes after loading and linking, but the actual >> destination module only has 393MB of MDNodes. There are 649-393MB (40% of >> 649MB) not used. >> >> MDNodes belong to the Context, deleting modules will not release the >> MDNodes. >> >> One possible...

...manman.ren at gmail.com> wrote: >> >>> Hi All, >>> >>> In LTO, we load in the source modules and link the source modules into >>> a destination module. >>> Lots of MDNodes are only used by the source modules, for example Xalan >>> used 649MB for MDNodes after loading and linking, but the actual >>> destination module only has 393MB of MDNodes. There are 649-393MB (40% of >>> 649MB) not used. >>> >>> MDNodes belong to the Context, deleting modules will not release the >>> MDNodes. >>&gt...

...wrote: >>> >>>> Hi All, >>>> >>>> In LTO, we load in the source modules and link the source modules into >>>> a destination module. >>>> Lots of MDNodes are only used by the source modules, for example Xalan >>>> used 649MB for MDNodes after loading and linking, but the actual >>>> destination module only has 393MB of MDNodes. There are 649-393MB (40% of >>>> 649MB) not used. >>>> >>>> MDNodes belong to the Context, deleting modules will not release the >>>>...

...ths ago 642MB r-base latest 4e55790c88ae 4 months ago 642MB r-base 3.6.0 6dfc0dec6d66 6 months ago 662MB r-base 3.5.3 62c848eeb175 8 months ago 649MB r-base 3.5.2 578644a0540c 10 months ago 650MB r-base 3.5.1 93ca38345db2 16 months ago 678MB r-base 3.5.0 fb43e8fe1667 17 months ago 698MB r-base...

Hi Today I did a clean Windows XP install on my partition, latest patches included. What perhaps is more interesting is that I was able to log the ENTIRE installation of EVE_Premium_Setup_185699_m.exe 649MB. After updating to (build?) 197121 I also logged some gameplay (3-8MB): Exiting station, warping to gate, changing jukebox track, dock to station og exit the game. Did not get to log the EULA window. Anyway the log contains directories, filenames, dll's and I think everything else accessed by...

Hello all, i am one of the maintainers of the open-source https://repo2docker.readthedocs.io/ tool. The tool builds a container image from a directory. Depending on what it finds in the directory it will install different software for the user. The focus of the tool is to make it easier for researchers to create environments in which their code runs and can then be used to share and reproduce