-
Notifications
You must be signed in to change notification settings - Fork 163
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
net: fix several unwraps of complex errors #1623
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1e0c58e
to
b043094
Compare
b043094
to
3aa358a
Compare
The number of places where no VSC chips are used, but the VSC types appear for various reasons, has turned this into quite a game of whack-a-mole. With any luck it will pass the build eventually; I keep failing to predict which builds are affected when I test locally (e.g. the nucleo h7 build winds up depending on the VSC error types). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like CI is happy now!
3aa358a
to
8c4dc9d
Compare
Updated numbers post-whackamole: Gimlet E net stack: -16,388 bytes |
This knocks a lot of flash off most netstack task sizes, by removing much of its dependence on the formatting machinery invoked by unwrap. (It's not all gone, because smoltcp still uses it.) Concretely, - Gimlet E net: -16,388 bytes - Monorail server: -8,820 bytes - Sidecar D net: -8 bytes, because something is still pulling in the goo.
8c4dc9d
to
96e885e
Compare
This knocks about 3.7 kiB (!) off Gimlet's netstack task size, by removing much of its dependence on the formatting machinery invoked by unwrap. (It's not all gone, because smoltcp still uses it.)