-
Notifications
You must be signed in to change notification settings - Fork 446
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Undefined behavior on 16 bit architectures #982
Comments
d2weber
added a commit
to d2weber/smoltcp
that referenced
this issue
Sep 10, 2024
d2weber
added a commit
to d2weber/smoltcp
that referenced
this issue
Sep 10, 2024
d2weber
added a commit
to d2weber/smoltcp
that referenced
this issue
Sep 10, 2024
d2weber
added a commit
to d2weber/smoltcp
that referenced
this issue
Sep 18, 2024
d2weber
added a commit
to d2weber/smoltcp
that referenced
this issue
Sep 18, 2024
d2weber
added a commit
to d2weber/smoltcp
that referenced
this issue
Sep 23, 2024
Fixed in #983 . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I checked out this crate and used it as a path dependency, cargo warns be about several places with undefined behavior.
To reproduce:
In a crate that uses a target with
"target-pointer-width": "16"
specify inCargo.toml
(assuming the directories are next to each other):When building/checking in the crate with the 16 bit target, cargo yields:
Note: if I specify the dependency as usual (
smoltcp= "0.10.0"
), these warnings won't appear but the behavior is still undefined.The text was updated successfully, but these errors were encountered: