search for: 58mb

Hi All, Type uniquing for C++ is in. Some data for Xalan with -flto -g: 9.9MB raw dwarf size, peak memory usage at 2.8GB The raw dwarf size was 58MB, memory usage was 7GB back in May, 2013. Other efforts at size reduction helped, and type uniquing improved on top of those. Data on building clang with "-flto -g" after type uniquing: 3.4GB MDNodes after parsing all bc files, 7GB MDNodes after linking all bc files 4.6GB DIEs 4G MC...

...r sending this summary and progress plans - it's great to see the > impact your changes have had and ideas for future direction. > > Type uniquing for C++ is in. Some data for Xalan with -flto -g: >> 9.9MB raw dwarf size, peak memory usage at 2.8GB >> The raw dwarf size was 58MB, memory usage was 7GB back in May, 2013. >> Other efforts at size reduction helped, and type uniquing improved on top >> of those. >> >> Data on building clang with "-flto -g" after type uniquing: >> 3.4GB MDNodes after parsing all bc files, 7GB MDNodes aft...

...ntermediate objects by default, i.e. it > generates both the binary and the IR in the intermediates files > and the static archives. Are you saying I should strip files? > What is the size of the final clang binary itself? Interestingly the non-LTO clang-3.9 is 49MB while the LTO one if 58MB. >> Also, given a fresh 3.9 install, on an otherwise gcc/libstdc++ system, >> how can I configure and build with -DLLVM_ENABLE_LTO=Thin? Is this >> supported, or does it require the use of some libXX too? > > You need to have Gold installed, but that is the same requirement...

Hi Manman, Thanks for sending this summary and progress plans - it's great to see the impact your changes have had and ideas for future direction. Type uniquing for C++ is in. Some data for Xalan with -flto -g: > 9.9MB raw dwarf size, peak memory usage at 2.8GB > The raw dwarf size was 58MB, memory usage was 7GB back in May, 2013. > Other efforts at size reduction helped, and type uniquing improved on top > of those. > > Data on building clang with "-flto -g" after type uniquing: > 3.4GB MDNodes after parsing all bc files, 7GB MDNodes after linking all >...

...st of lists. In the expression tokens[[i.d]][[i.s]], the first index runs over 1697 reports, the second over the sentences in the report, each of which consists of a vector of tokens, i.e., the character strings between the white spaces in the sentence. One of the largest reports takes up 58MB on the harddisk. Thus, the number of sentences can be quite large, and some of the sentences are quite long (measure in tokens as well as in characters). * stopwords: is a vector of 571 words that occur very often in written English. The code operates on sentences, converting each token in...

...ry and progress plans - it's great to see >> the impact your changes have had and ideas for future direction. >> >> Type uniquing for C++ is in. Some data for Xalan with -flto -g: >>> 9.9MB raw dwarf size, peak memory usage at 2.8GB >>> The raw dwarf size was 58MB, memory usage was 7GB back in May, 2013. >>> Other efforts at size reduction helped, and type uniquing improved on >>> top of those. >>> >>> Data on building clang with "-flto -g" after type uniquing: >>> 3.4GB MDNodes after parsing all bc fi...

...1 ${CWD}/${WORKDIR}/ +#cp -p ${CWD}/$1 ${CWD}/${WORKDIR}/ cp -p ${CWD}/Makefile ${CWD}/${WORKDIR}/ cp -p ${CWD}/build-kernel-injail.sh ${CWD}/${WORKDIR}/ cp -p ${CWD}/list ${CWD}/${WORKDIR}/ you were overwriting the kernel config you adjusted the MINIROOTSIZE before?! i was able to get up to a 58mb ramdisks on that board without failure at startup. please tell me if you are interested in any dmesg/kernelconfig/whatever listings for your configs. greets adrian

...rently related (?) problem occurs. Yesterday, I started working on some simulations I have done (with R of course! :-) ). I did exactly the same operations on rukbat and mirfak (using ESS-elsewhere while sitting on alnair), starting with the same calls, vsize=80M, nsize=800k, no-restore. I loaded a 58MB file with load, and there are a few variables with arrays of htest-objects. Then, I did as.vector(sapply(chisq5M11000, function(x) x$statistic)) to get a vector of the test statistics. Now, occasionally, it prints a nice vector with all the values intact. Occasionally, one of the entries are NULL,...

Hi list, I am trying to install FreeBSD 9.1-Release amd64 on a Supermicro server: SuperStorage Server 6027R-E1R12N with Intel Xeon E5-2640 CPU and 32 GB (4 x 8 ) KVR16R11D4/8HC installed Currently I have only 2 SSD Kingston drives (working in mirror) installed on that server. during booting installer from the ISO CD (amd64), the boot process fails with message: Mounting from

I tried building llvm, clang, lld, lldb from the 3.9 svn release branch with LTO, and some of the results were unexpected. I first tried to rebuild llvm with llvm-3.9, which has ThinLTO, by providing -DLLVM_ENABLE_LTO=Thin, but that failed very quickly, so I fell back to building with -DLLVM_ENABLE_LTO=On and using the system CC/CXX (gcc 6.1). The resulting installed build is many times bigger

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, i have two systems, A (Solaris 10 update 5) and B (Solaris 10 update 6). i''m using ''zfs send -i'' to replicate changes on A to B. however, the ''zfs recv'' on B is running extremely slowly. if i run the zfs send on A and redirect output to a file, it sends at 2MB/sec. but when i use ''zfs send

...?. I am getting basically the same result whether it is single zfs drive, mirror or a stripe (I am testing with two Seagate 7200.10 320G drives hanging off the same interface card). On the test machine I also have an old disk with UFS on PATA interface (Seagate 7200.7 120G). dd from raw disk gives 58MB/s and dd from file on UFS gives 45MB/s - far less relative slowdown compared to raw disk. This is just an AthlonXP 2500+ with 32bit PCI SATA sil3114 card, but nonetheless, the hardware has the bandwidth to fully saturate the hard drive, as seen by dd from the raw disk device. What is going on? Am...