frederik
/
xserver
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

(!1909) fb: use calloc() instead of malloc() 

Using calloc() instead of malloc() as preventive measure, so there
never can be any hidden bugs or leaks due uninitialized memory.

The extra cost of using this compiler intrinsic should be practically
impossible to measure - in many cases a good compiler can even deduce
if certain areas really don't need to be zero'd (because they're written
to right after allocation) and create more efficient machine code.

The code pathes in question are pretty cold anyways, so it's probably
not worth even thinking about potential extra runtime costs.

Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
This commit is contained in:
Enrico Weigelt, metux IT consult 2025-04-10 19:13:18 +02:00
parent 3fb4415fd8
commit e64a51188a
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
fb/fboverlay.c
View File

@ -260,7 +260,6 @@ fbOverlayFinishScreenInit(ScreenPtr pScreen,
int nvisuals;
int ndepths;
VisualID defaultVisual;
FbOverlayScrPrivPtr pScrPriv;
if (!dixRegisterPrivateKey
(&fbOverlayScreenPrivateKeyRec, PRIVATE_SCREEN, 0))
@ -269,7 +268,7 @@ fbOverlayFinishScreenInit(ScreenPtr pScreen,
if (bpp1 == 24 || bpp2 == 24)
return FALSE;
pScrPriv = malloc(sizeof(FbOverlayScrPrivRec));
FbOverlayScrPrivPtr pScrPriv = calloc(1, sizeof(FbOverlayScrPrivRec));
if (!pScrPriv)
return FALSE;