search for: switch2

...bout this example: https://godbolt.org/g/iSUjKD but it doesn't compile, but Krzysztof figured out this one: https://godbolt.org/g/lYQFBd (BTW it seems that clang is pretty bad at cleaning out iostreams) struct A { const int x; }; union B { A a1; A a2; B() : a1{42} { } void switch2(int x) { a1.~A(); new (&a2) A{x}; } }; int main() { B b; std::cout << b.a1.x << std::endl; b.switch2(50); std::cout << b.a2.x << std::endl; } As he checked in standard, it seems to be valid C++11 code by *9.5.4*. So as you can see di...

...xample: https://godbolt.org/g/iSUjKD but > it doesn't compile, but Krzysztof figured out this one: > https://godbolt.org/g/lYQFBd (BTW it seems that clang is pretty bad at > cleaning out iostreams) > > struct A { const int x; }; union B { A a1; A a2; B() : a1{42} { } void > switch2(int x) { a1.~A(); new (&a2) A{x}; } }; int main() { B b; > std::cout << b.a1.x << std::endl; b.switch2(50); std::cout << b.a2.x > << std::endl; } > As he checked in standard, it seems to be valid C++11 code by *9.5.4*. > So as you can see different groups w...

...nted, allowing for a maximum MTU of 1500 (1504 with the tag, I assume). Untagged frames larger than 1462 bytes will not make it through the GRE tunnel setup. 192.168.200.6 192.168.200.2 (802.1q switch1)<->(eth0-br0-gretap)<->(gretap-br0-eth0)<->(802.1q switch2) 10.0.0.0/12 is my 'untagged' subnet. (default vlan 1, untagged) 192.168.7.0/32 is my tagged subnet. (vlan 800, tagged) The host I use to test has a NIC in each subnet and is hooked to switch1, it is pinging hosts on switch2. First, tagged packets: $ ping -c 3 -M do -s 1472 192.168.7.1...

2017-01-26 3:28 GMT+01:00 Richard Smith <richard at metafoo.co.uk>: > On 25 January 2017 at 15:03, Hal Finkel via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > >> Hi Piotr, >> >> I think makes sense. Modulo bitcasts, the invariant is identified by a >> particular pointer SSA value. Given that you can't sensibly have two >> nonequivalent

...cases that are actually hot. > > SWITCH1: > switch(val) { > HOT: ... > COLD1: ... > COLD2: ... > .... > COLDN: ... > default: ... > } > > would get transformed into: > > > SWITCH1: > switch(val) { > HOT: ... > default: > br SWITCH2: > } > > SWITCH2: > switch(val) { > COLD1: ... > COLD2: ... > .... > COLDN: ... > default: ... > } > > > This is profile based switch peeling -- which is a separate optimization from partial inlining. David > On Tue, Aug 15, 2017 at 1:14 PM...

Hi Jessica, Thanks for the feedback. I believe the existing partial inliner pass does use some common utilities like the code extractor to do outlining. Is that what you're referring to? I don't recall seeing any other passes that has outlining other than the machine outliner, but I may have missed something. I briefly looked at River's RFC and it seems he's mainly utilizing