IPv6 failure in "mip_test" #3443
-
|
I have built the ASSERT(i6->src[0] == mg_htonll(0x1000000000000000) && i6->src[1] == 0 && i6->dst[0] == mg_htonll(0x2000000000000000) && i6->dst[1] == 0);Splitting up: ASSERT(i6->src[0] == mg_htonll(0x1000000000000000));
ASSERT(i6->src[1] == 0);
ASSERT(i6->dst[0] == mg_htonll(0x2000000000000000));
ASSERT(i6->dst[1] == 0);I see it is But why? |
Beta Was this translation helpful? Give feedback.
Answered by
scaprile
Feb 19, 2026
Replies: 1 comment 2 replies
-
|
No idea, I never thought on Windows nor possible compiler issues, and it even runs on VC98. Without seeing what the value of i6->dst is... |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Well, there is your problem...
The reason for the existence of mip_test is to be able to test the stack low-level functions. We test in Linux, and we add a couple of big-endian architectures. Then we test on VC98 to have a taste on a C89 compiler. We don't actually care about other compilers, the stack functional test is done with mip_tap_test (Linux) and mip_port_test (big-endians).
If fixing the reason for your failure does not interfere with our use of this test, we'll gladly add it. Currently it has no use for us. You can always try to convince us otherwise, of course.