search for: grew

...12-CURRENT [1], from trunk r250000 (2015-10-11) all through r327700 (2018-03-16), with increments of 100 revisions. This is mainly meant as an archive, for easily doing bisections, but there are also some interesting statistics. From r250000 through r327700: * the total (stripped) executable size grew by approximately 43% * the size of the text segment grew by approximately 41% * the size of the data segment grew by approximately 61% * the size of the bss segment grew by approximately 185% * real build time (on a 32 core system) grew by approximately 60% * user build time (on a 32 core system) g...

...nk r250000 (2015-10-11) all through r327700 (2018-03-16), with > increments of 100 revisions. This is mainly meant as an archive, for > easily doing bisections, but there are also some interesting statistics. > > From r250000 through r327700: > * the total (stripped) executable size grew by approximately 43% > * the size of the text segment grew by approximately 41% > * the size of the data segment grew by approximately 61% > * the size of the bss segment grew by approximately 185% > * real build time (on a 32 core system) grew by approximately 60% > * user build tim...

...hrough r327700 >> (2018-03-16), with increments of 100 revisions. This is mainly meant as an >> archive, for easily doing bisections, but there are also some interesting >> statistics. >> >> From r250000 through r327700: >> * the total (stripped) executable size grew by approximately 43% >> * the size of the text segment grew by approximately 41% >> * the size of the data segment grew by approximately 61% >> * the size of the bss segment grew by approximately 185% >> * real build time (on a 32 core system) grew by approximately 60% >&...

...from trunk r250000 (2015-10-11) all through r327700 (2018-03-16), with increments of 100 revisions. This is mainly meant as an archive, for easily doing bisections, but there are also some interesting statistics. > > From r250000 through r327700: > * the total (stripped) executable size grew by approximately 43% > * the size of the text segment grew by approximately 41% > * the size of the data segment grew by approximately 61% > * the size of the bss segment grew by approximately 185% > * real build time (on a 32 core system) grew by approximately 60% > * user build tim...

...gt; (2018-03-16), with increments of 100 revisions. This is mainly meant as an >>> archive, for easily doing bisections, but there are also some interesting >>> statistics. >>> >>> From r250000 through r327700: >>> * the total (stripped) executable size grew by approximately 43% >>> * the size of the text segment grew by approximately 41% >>> * the size of the data segment grew by approximately 61% >>> * the size of the bss segment grew by approximately 185% >>> * real build time (on a 32 core system) grew by approxi...

Hello LLVM, Does the community have bots or humans tracking code size for -Os builds? I've noticed troubling regressions lately. Sometime near Nov 5, the EEMBC bitmnp01 benchmark grew by 25% for ARMv7m and 35% for i586. That's ghastly. This week, the EEMBC matrix01 workload grew by 5% for ARMv7m and 3% for i586. Regards, -steve

Hi. Last night the /var/lib/puppet/clientbucktet directory on one of our production servers suddenly grew about 4 GB, filling up the entire /var partition. Around that time, I see that there was a problem with one of our CIFS mount points (i.e. our CIFS client had problems reaching our CIFS server). We''re using puppet to set up the CIFS mount point. Under the clientbucket folder, I have a gre...

I need a way to convert files that I save with Firefox as a 'print to file' to 'pdf' I tried 'convert' but that rendered the text as graphics which grew the file and wasn't what I wanted. How would someone accomplish this - or can I just print to a PDF? Craig

...t; builds? > > Hi Steve, > > I still haven't got around doing a CI for EEMBC or SPEC on ARM. I do > track performance every release, but not code size at -Os. > >> I've noticed troubling regressions lately. Sometime near Nov >> 5, the EEMBC bitmnp01 benchmark grew by 25% for ARMv7m and 35% for >> i586. That's ghastly. This week, the EEMBC matrix01 workload grew by >> 5% for ARMv7m and 3% for i586. > > Hum, v7M is even lower priority for me at the moment. :) > > Though, I have to say, 25% is really bad. Can you bisect to see whic...

...SQL queries, optimization remarks can give you similar information, albeit at the IR level.) As another example, this code size tool can attribute code size to semantically interesting groups of code, like C++/Swift classes, or files. In the diff mode, you can see how the code size of a class/file grew compared to a baseline. The tool understands inheritance, so you can also see interesting high-level trends. E.g `clang::Sema` grew more than `llvm::Pass` between clang-6 and clang-7. Unlike bloaty, this tool focuses exclusively on the text segment. Also unlike bloaty, it uses LLVM's DWARF par...

Dear R developers, i've got a question concerning an embedded R instance. I called the initialization routines as seen in the "writing extensions" guide (Rf_initialize, setup_Rmainloop and R_ReplDLLinit). I also changed the function callback pointer of readconsole and writeconsoleex to my local functions. when i call mainloop there is no problem and the commands are evaluated

...> remarks can give you similar information, albeit at the IR level.) > > As another example, this code size tool can attribute code size to semantically > interesting groups of code, like C++/Swift classes, or files. In the diff mode, > you can see how the code size of a class/file grew compared to a baseline. The > tool understands inheritance, so you can also see interesting high-level trends. > E.g `clang::Sema` grew more than `llvm::Pass` between clang-6 and clang-7. > > Unlike bloaty, this tool focuses exclusively on the text segment. Also unlike > bloaty, it...

...n give you similar information, albeit at the IR level.) >> >> As another example, this code size tool can attribute code size to semantically >> interesting groups of code, like C++/Swift classes, or files. In the diff mode, >> you can see how the code size of a class/file grew compared to a baseline. The >> tool understands inheritance, so you can also see interesting high-level trends. >> E.g `clang::Sema` grew more than `llvm::Pass` between clang-6 and clang-7. >> >> Unlike bloaty, this tool focuses exclusively on the text segment. Also unlike...

I have tried various mail clients to read the Rails mailing list for the past 12 months. As the list volume grew, it became utterly impossible to browse through the new messages and very hard to locate the useful gems I had previously found. After subscribing to a few more lists, I realized that there had to be a better way. I could not find anything to meet my needs, so I designed DevLists, which, t...

...d (12GB) mailbox and issued a ?doveadm sync -u $user -N -U tcps:hostB` so that I would expect the hostB to reach around 100mb-ish of email. I let it go for a little and saw that the mail was done. When I issued a simple ?df -h? on the directory, it was already multiple 100mb?s large and growing. It grew back to multiple GB in little time. Again the Junk mailbox was the culprit. In the mean time I noticed my mailclient downloading 44k mails in that mailbox (where there were only a few in the Junk mailbox normally). I again vaporized the entire mailbox on hostB and cleaned out Junk and issued a man...

Over time, the Wine wiki front page grew rather unwieldy, so I split the developer information off into two new pages, leaving only a simplified front page behind, mostly aimed at users. It's radically simpler. Hopefully it'll be more welcoming to new users. Comments?

...> redesigns are required, and then asking for a fresh start makes sense. There is an (ever growing) patch series that connects contributions by multiple people with patches in all sorts of states, from merged to WIP: The first was this one https://reviews.llvm.org/D69785, since then the series grew in all directions (see the stack). I have other (=smaller) patch series that evolve over time but this one is the biggest and most complex. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: not av...

...ny given time. It’s now possible to access remarks through object files. So, I thought it would be an interesting experiment to write a C++ tool using the new remarks API to write a simple size tool. A size tool using remarks would be able to tell us about the following things: 1) Which functions grew the most in size between one compilation and another compilation 2) Which functions were/were not inlined between compilations (and similar insights into other passes) 3) Which compiler passes caused the largest increases in each function I have a prototype for a size tool which accomplishes (1) u...

I have a large dial plan here with over 3000 lines, and several dozen macros. As it grew, it became apparent that there was some problems. 1. When you pass arguments to a macro in the form of $ARG1, $ARG2 etc, if that macro calls another macro, and passes arguments like this as well, you lose the original values. 2. When the macro's 'return' some value, it has to set a...

...41245092 2% /usr /dev/da0s1d 4298926 187570 3767442 5% /var Notice the the increase in the root partition. Should I have made this partition bigger when I first installed? Is there any cleaning up I can do after version upgrades? I would've thought /usr would be the one that grew more, but then again my /usr partition is fairly sizeable. Does 7.0 just take up a lot more of the root partition than 6.2? - Gavin