<feed xmlns='http://www.w3.org/2005/Atom'>
<title>fortify-headers/tests/test_sprintf.c, branch experimental</title>
<subtitle>Standalone portable header-based implementation of FORTIFY_SOURCE=3 
</subtitle>
<id>http://git.dustri.org/fortify-headers/atom?h=experimental</id>
<link rel='self' href='http://git.dustri.org/fortify-headers/atom?h=experimental'/>
<link rel='alternate' type='text/html' href='http://git.dustri.org/fortify-headers/'/>
<updated>2024-09-06T11:38:22Z</updated>
<entry>
<title>Work around a gcc warning</title>
<updated>2024-09-06T11:38:22Z</updated>
<author>
<name>jvoisin</name>
</author>
<published>2024-09-06T11:36:15Z</published>
<link rel='alternate' type='text/html' href='http://git.dustri.org/fortify-headers/commit/?id=f2e7f24daaa43c0927130b6ed02c3ed17689b3ca'/>
<id>urn:sha1:f2e7f24daaa43c0927130b6ed02c3ed17689b3ca</id>
<content type='text'>
It seems that annotating sprintf with `write` makes gcc unhappy, as its
analyser is unable to understand that we're checking if `__b != -1` before
calling `__orig_snprintf`, so let's comment this annotation for now.
</content>
</entry>
</feed>
