search for: 141m

...t LLVM libraries and everything else being in separate repos. I agree fully. I work on a project that use submodules for external dependencies. For llvm this means compiling and linking statically with dependencies for Linux and OSX platforms. So these: (compiler-rt, libcxx, libcxxabi, libunwind) 141M (.git 60M) I would hesitate to add a dependency that use 1.5G disk space, so if you go with the mono-repo approach I would probably use the supposed read only mirror repos for these modules. This in turn would mean that the hurdle for contributing back to these projects would increase and thus t...

...c 452M clang-include-fixer 444M modularize 443M clang-func-mapping 442M clang-diff 441M libToolingExample00 438M pp-trace 434M diagtool 184M llvm-cfi-verify 170M llvm-objdump 168M sancov 158M llvm-rtdyld 149M llvm-ar 148M llvm-nm 145M llvm-extract 145M llvm-link 142M llvm-dwarfdump 141M llvm-split 131M llvm-mc 127M llvm-pdbutil 126M clang-offload-bundler 122M llvm-mca 121M verify-uselistorder 121M llvm-cat 120M llvm-as 117M llvm-special-case-list-fuzzer 117M llvm-demangle-fuzzer 116M llvm-modextract 114M obj2yaml 112M llvm-xray 105M sanstats 105M llvm-symbolizer 96...

...> 442M clang-diff > 441M libToolingExample00 > 438M pp-trace > 434M diagtool > 184M llvm-cfi-verify > 170M llvm-objdump > 168M sancov > 158M llvm-rtdyld > 149M llvm-ar > 148M llvm-nm > 145M llvm-extract > 145M llvm-link > 142M llvm-dwarfdump > 141M llvm-split > 131M llvm-mc > 127M llvm-pdbutil > 126M clang-offload-bundler > 122M llvm-mca > 121M verify-uselistorder > 121M llvm-cat > 120M llvm-as > 117M llvm-special-case-list-fuzzer > 117M llvm-demangle-fuzzer > 116M llvm-modextract > 114M obj2yaml &g...

...are empty. Chain INPUT (policy ACCEPT 359K packets, 136M bytes) pkts bytes target prot opt in out source destination Chain FORWARD (policy ACCEPT 55801 packets, 4736K bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 319K packets, 141M bytes) pkts bytes target prot opt in out source destination -- Stephen Clark

...vant, this is a 6 drive mirrored pool with a single SSD for L2Arc cache. Pool version 26 under Nexenta Core Platform 3.0 with a LSI 9200-16E and SATA disks. $ zpool status bigboy pool: bigboy state: ONLINE scan: scrub in progress since Sat Feb 5 02:22:18 2011 3.74T scanned out of 3.74T at 141M/s, 0h0m to go 37.9M repaired, 99.88% done [-----config snip - all columns 0, one drive on the right has "(repairing)"----] errors: No known data errors And then once the scrub completes: $ zpool status bigboy pool: bigboy state: ONLINE scan: scrub repaired 37.9M in 7h42m with 0...

Hi List, I am running into a problem where I have 2 interfaces bridged with and ip address assigned. I have another interface in which traffic has ingress traffic that needs to go out the bridged interface. I am trying unsuccessfully to SNAT the traffic leaving the bridge interface to its assigned address. # brctl show xbrdg0 bridge name bridge id STP enabled interfaces

Hello everyone, 9.0.0-rc3 was tagged today from the release_90 branch at r370450. In the Git monorepo, it's tagged as llvmorg-9.0.0-rc3. Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc3 Binaries will be added as they become available. There are currently no open release blockers, which means if nothing new comes up, the final release could ship soon and this is

On Jan 13, 2017, at 1:37 PM, Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> wrote: > The main outcome of the BoF had the dev meeting was that we agree’d that moving to GitHub was the best choice forward for LLVM (IIRC only one person in the room expressed concerned about GitHub, but he said he had personal grief with them and nothing specific for LLVM). > > The unknown that

I have to match my packets based on MAC address, which I cannot do in the POSTROUTING chain, so I do it in PREROUTING using MARK. Then, I match on the MARK in the POSTROUTING chain to do a CLASSIFY. But this does not seem to work: wireless-r1 bwlimit # iptables -L -v -n -t mangle Chain PREROUTING (policy ACCEPT 3353K packets, 941M bytes) pkts bytes target prot opt in out source