search for: origf

...d functions, sees if they're from the loaded module, and then materializes them. Is this the best way to handle JITing code from a lazily loaded module or is there a better way to handle this? It seems like this could be handled easily by moveFunctionBody if it just did something like: if (OrigF.isMaterializable()) { OrigF.materialize(); } Is there a way to add a hook into the JIT to handle this kind of materialization? Thanks, Brian -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161213/f3...

...acket of %d bytes to %s (%s)", packet->len, dest->name, dest->hostname); offset = DATA(packet) + ether_size + ip_size; - maxlen = (dest->mtu - ether_size - ip_size) & ~0x7; + maxlen = (MAX(dest->mtu, 590) - ether_size - ip_size) & ~0x7; ip_off = ntohs(ip.ip_off); origf = ip_off & ~IP_OFFMASK; ip_off &= IP_OFFMASK;

...f738..b1a6389 100644 --- a/src/route.c +++ b/src/route.c @@ -317,6 +317,7 @@ static void fragment_ipv4_packet(node_t *dest, vpn_packet_t *packet) { struct ip ip; vpn_packet_t fragment; + fragment.flag_bits =3D packet->flag_bits; int len, maxlen, todo; uint8_t *offset; uint16_t ip_off, origf; ------=_NextPart_000_0001_01CBADF1.BD635B80--