# stage2: add an explicit padding field to avoid Valgrind warning · gitcafe/zig

[View on GitCafe](https://git.cafe/gitcafe/zig/commit/3d9b6cfcc9341cef40a8a525a4acf8be8b81992c)

Repository: [gitcafe/zig](https://git.cafe/gitcafe/zig)

Visibility: public

Requested revision: 3d9b6cfcc9341cef40a8a525a4acf8be8b81992c

Requested commit: 3d9b6cfcc9341cef40a8a525a4acf8be8b81992c

Commit: 3d9b6cfcc9341cef40a8a525a4acf8be8b81992c

Tree: 4ac796abca2c07800e7438bdf71c6d517e9c0f4e

Author: Andrew Kelley

Committer: Andrew Kelley

## Message

```
stage2: add an explicit padding field to avoid Valgrind warning

Adds a `unused: u32 = 0` field to `Zir.Header`.

We could leave this as padding, however it triggers a Valgrind warning because
we read and write undefined bytes to the file system. This is harmless, but
it's essentially free to have a zero field here and makes the warning go away,
making it more likely that following Valgrind warnings will be taken seriously.

```

## Parents

- [56129d26ebd8c54563e92a78b9dab20f69dbc646](https://git.cafe/gitcafe/zig/commit/56129d26ebd8c54563e92a78b9dab20f69dbc646?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zig/tree/3d9b6cfcc9341cef40a8a525a4acf8be8b81992c?format=markdown)