mirror of
https://github.com/ziglang/zig.git
synced 2025-12-30 01:53:16 +00:00
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.
This commit is contained in:
parent
56129d26eb
commit
3d9b6cfcc9
@ -43,7 +43,11 @@ pub const Header = extern struct {
|
||||
instructions_len: u32,
|
||||
string_bytes_len: u32,
|
||||
extra_len: u32,
|
||||
|
||||
/// 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.
|
||||
unused: u32 = 0,
|
||||
stat_inode: std.fs.File.INode,
|
||||
stat_size: u64,
|
||||
stat_mtime: i128,
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user