search for: 4gigs

This year Igor Kudrin put in a lot of work in enabling DWARF64 support in LLVM. At Facebook we are looking into it as one of the options for handling debug information over 4gigs in production environment. One concern is that due to mix of third party libraries and llvm compiled code the final library/binary will have a mix of CU that are DWARF32/64. This is supported by DWARF format. With this mix it is possible that even with DWARF64 enabled one can still encounter reloca...

Greetings, Can anyone confirm that R can access more than 2GB of virtual memory on Windows? We are in the process of porting a memory-hungry routine from Linux. We are using R 1.8.1 on Windows 2000 Advanced Server; we've set the 3GB switch in boot.ini, and rebooted twice. We have run editbin against Rgui.exe ad Rterm.exe and confirmed the header settings with dumpbin.exe. We are invoking R

Hello, ? Are there some basic things one can do to speed up a R code? I am new to R and currently going through the following situation. ? I have run a R code on two different machines. I have R 2.12 installed on both. ? Desktop 1 is slightly older and has a dual core processor with 4gigs of RAM. Desktop 2 is newer one and has a xeon processor W3505 with 12gigs of RAM. Both run on Windows 7. ? I don't really see any significant speed up in the newer computer (Desktop 2). In the older one the program took around 5hrs 15 mins and in the newer one it took almost 4hrs 30mins. ?In...

To much of my dissapointment, the uptime on my TxD account does not improve. What alternatives do we have for hosting Rails projects on shared accounts? I would love to keep lighttpd and the level of control I have on TxD but wouldn''t like to spend much more (I am currently on the 25$/month plan). I won''t need much support, but I would love to have subversion

...n Wed, Nov 11, 2020 at 12:19 AM Alexander Yermolovich via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> This year Igor Kudrin put in a lot of work in enabling DWARF64 support in LLVM. At Facebook we are looking into it as one of the options for handling debug information over 4gigs in production environment. One concern is that due to mix of third party libraries and llvm compiled code the final library/binary will have a mix of CU that are DWARF32/64. This is supported by DWARF format. With this mix it is possible that even with DWARF64 enabled one can still encounter reloca...

On Wed, Nov 11, 2020 at 12:19 AM Alexander Yermolovich via llvm-dev < llvm-dev at lists.llvm.org> wrote: > This year Igor Kudrin put in a lot of work in enabling DWARF64 support in > LLVM. At Facebook we are looking into it as one of the options for handling > debug information over 4gigs in production environment. One concern is that > due to mix of third party libraries and llvm compiled code the final > library/binary will have a mix of CU that are DWARF32/64. This is supported > by DWARF format. With this mix it is possible that even with DWARF64 > enabled one can st...

...0 at 12:19 AM Alexander Yermolovich via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> >> >> This year Igor Kudrin put in a lot of work in enabling DWARF64 support in LLVM. At Facebook we are looking into it as one of the options for handling debug information over 4gigs in production environment. One concern is that due to mix of third party libraries and llvm compiled code the final library/binary will have a mix of CU that are DWARF32/64. This is supported by DWARF format. With this mix it is possible that even with DWARF64 enabled one can still encounter reloca...

...ction. So when adding an orphan section we would have another loop iterating over inputSections. We can reuse the dependentSections to have this piece of information (generalizing the existing special case for -r/--emit-relocs) > This way as long as DWARF32 sections don't themselves go over 4gigs, the final binary can contain debug information that exceeds 4gig. > Which I think will be the common case. I would not expect the linker behaves differently when linking a few additional sections change the behavior so drastically in a not-easily-explainable way. This deserves a dedicated link...

...19 AM Alexander Yermolovich via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> > >> This year Igor Kudrin put in a lot of work in enabling DWARF64 support > in LLVM. At Facebook we are looking into it as one of the options for > handling debug information over 4gigs in production environment. One > concern is that due to mix of third party libraries and llvm compiled code > the final library/binary will have a mix of CU that are DWARF32/64. This is > supported by DWARF format. With this mix it is possible that even with > DWARF64 enabled one can st...

...ction. So when adding an orphan section we would have another loop iterating over inputSections. We can reuse the dependentSections to have this piece of information (generalizing the existing special case for -r/--emit-relocs) > This way as long as DWARF32 sections don't themselves go over 4gigs, the final binary can contain debug information that exceeds 4gig. > Which I think will be the common case. I would not expect the linker behaves differently when linking a few additional sections change the behavior so drastically in a not-easily-explainable way. This deserves a dedicated link...

...ermolovich via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > >> >> > >> >> This year Igor Kudrin put in a lot of work in enabling DWARF64 > support in LLVM. At Facebook we are looking into it as one of the options > for handling debug information over 4gigs in production environment. One > concern is that due to mix of third party libraries and llvm compiled code > the final library/binary will have a mix of CU that are DWARF32/64. This > is supported by DWARF format. With this mix it is possible that even with > DWARF64 enabled one can st...

...ctively compare the cases online with my results. I''ve included some of the output included in previous cases. I''ve attached a ''zdb -e -dddd tank'' and tried to run a ''zdb -e -bb tank'' however it ran out of RAM and I can''t add more than 4gigs to this system. I''d greatly appreciate any help anyone is able to provide. Thanks, Berant ############################################################################### nmc at nexenta1:/$ show volume import VOLUME:ID STATE D LUNS tank:13362623912425247739...

I am [trying to] perform a test prior to moving my data to solaris and zfs. Things are going very poorly. Please suggest what I might do to understand what is going on, report a meaningful bug report, fix it, whatever! Both to learn what the compression could be, and to induce a heavy load to expose issues, I am running with compress=gzip-9. I have two machines, both identical 800MHz P3 with