| View previous topic :: View next topic |
| Author |
Message |
hjkl
Apprentice
Joined: 22 Apr 2021
Posts: 198
Location: Somewhere in Europe
|
 Posted: Fri Jul 23, 2021 4:52 pm Post subject: Getting lots of messages/notes when compiling the kernel |
 |
|
Hi there,
I'm currently at the stage of reinstalling Gentoo from within Arch (via chroot) on a hardened profile and I just finished compiling it.
On the way though, I noticed it gave me lots of messages/notes that are all the same (As in, the message )
| Code: | | byref variable will be forcibly initialized |
Examples:
| Code: |
23 | struct nvif_timer_wait _wait; \
| ^~~~~
./drivers/gpu/drm/nouveau/include/nvif/timer.h:33:32: note: in expansion of macro ‘nvif_nsec’
33 | #define nvif_usec(d,u,cond...) nvif_nsec((d), (u) * 1000, ##cond)
| ^~~~~~~~~
./drivers/gpu/drm/nouveau/include/nvif/timer.h:34:32: note: in expansion of macro ‘nvif_usec’
34 | #define nvif_msec(d,m,cond...) nvif_usec((d), (m) * 1000, ##cond)
| ^~~~~~~~~
drivers/gpu/drm/nouveau/dispnv50/ovly827e.c:72:13: note: in expansion of macro ‘nvif_msec’
72 | s64 time = nvif_msec(device, 2000ULL,
| ^~~~~~~~~
In file included from ./drivers/gpu/drm/nouveau/include/nvif/mmu.h:3,
from ./drivers/gpu/drm/nouveau/include/nvif/mem.h:3,
from drivers/gpu/drm/nouveau/dispnv50/disp.h:4,
from drivers/gpu/drm/nouveau/dispnv50/wndw.h:4,
from drivers/gpu/drm/nouveau/dispnv50/ovly.h:3,
from drivers/gpu/drm/nouveau/dispnv50/ovly.c:22:
drivers/gpu/drm/nouveau/dispnv50/ovly.c: In function ‘nv50_ovly_new’:
./drivers/gpu/drm/nouveau/include/nvif/object.h:81:22: note: byref variable will be forcibly initialized
81 | struct nvif_sclass *sclass; \
| ^~~~~~
drivers/gpu/drm/nouveau/dispnv50/ovly.c:46:8: note: in expansion of macro ‘nvif_mclass’
46 | cid = nvif_mclass(&disp->disp->object, ovlys);
| ^~~~~~~~~~~
drivers/gpu/drm/nouveau/dispnv50/ovly507e.c: In function ‘ovly507e_new_’:
drivers/gpu/drm/nouveau/dispnv50/ovly507e.c:175:44: note: byref variable will be forcibly initialized
175 | &(struct nvif_notify_uevent_req) {},
| ^
drivers/gpu/drm/nouveau/dispnv50/ovly507e.c:154:20: note: byref variable will be forcibly initialized
154 | struct nv50_wndw *wndw;
| ^~~~
drivers/gpu/drm/nouveau/nouveau_dma.c: In function ‘nv50_dma_wait’:
drivers/gpu/drm/nouveau/nouveau_dma.c:125:11: note: byref variable will be forcibly initialized
125 | int ret, cnt = 0;
| ^~~
drivers/gpu/drm/nouveau/nouveau_dma.c:124:11: note: byref variable will be forcibly initialized
124 | uint64_t prev_get = 0;
| ^~~~~~~~
drivers/gpu/drm/nouveau/nouveau_dma.c: In function ‘nouveau_dma_wait’:
drivers/gpu/drm/nouveau/nouveau_dma.c:168:6: note: byref variable will be forcibly initialized
168 | int cnt = 0, get;
| ^~~
drivers/gpu/drm/nouveau/nouveau_dma.c:167:11: note: byref variable will be forcibly initialized
167 | uint64_t prev_get = 0;
| ^~~~~~~~
drivers/gpu/drm/nouveau/nouveau_fence.c: In function ‘nouveau_fence_context_new’:
drivers/gpu/drm/nouveau/nouveau_fence.c:201:44: note: byref variable will be forcibly initialized
201 | &(struct nvif_notify_uevent_req) { },
| ^
drivers/gpu/drm/nouveau/nouveau_abi16.c: In function ‘nouveau_abi16’:
drivers/gpu/drm/nouveau/nouveau_abi16.c:48:24: note: byref variable will be forcibly initialized
48 | struct nv_device_v0 args = {
| ^~~~
drivers/gpu/drm/nouveau/nouveau_fence.c: In function ‘nouveau_fence_wait_legacy’:
drivers/gpu/drm/nouveau/nouveau_fence.c:272:11: note: byref variable will be forcibly initialized
272 | ktime_t kt;
| ^~
drivers/gpu/drm/nouveau/nouveau_fence.c: In function ‘nouveau_fence_new’:
drivers/gpu/drm/nouveau/nouveau_fence.c:418:24: note: byref variable will be forcibly initialized
418 | struct nouveau_fence *fence;
| ^~~~~
drivers/gpu/drm/nouveau/nouveau_abi16.c: In function ‘nouveau_abi16_ioctl_grobj_alloc’:
drivers/gpu/drm/nouveau/nouveau_abi16.c:431:22: note: byref variable will be forcibly initialized
431 | struct nvif_sclass *sclass;
| ^~~~~~
drivers/gpu/drm/nouveau/nouveau_chan.c: In function ‘nouveau_channel_idle’:
drivers/gpu/drm/nouveau/nouveau_chan.c:65:25: note: byref variable will be forcibly initialized
65 | struct nouveau_fence *fence = NULL;
| ^~~~~
|
.config: https://0x0.st/-VCH.txt
Is this anything to worry about?
I found the same on here https://bbs.archlinux.org/viewtopic.php?id=264403 but didn't find anything useful out of it.
Thanks.
_________________
Having problems compiling since 2021  |
|
| Back to top |
|
 |
alamahant
Advocate
Joined: 23 Mar 2019
Posts: 3879
|
| Posted: Fri Jul 23, 2021 7:47 pm Post subject: |
|
|
You compiled via genkernel?
I think there is nothing to worry about.
These are normal build output similar to when compiling any package via emerge.
After the build you should have run
if the exit status is 0 all is ok.
Why dont you use
| Code: |
make menuconfig
make
sudo make modules_install
sudo make install
|
without using an intermediary?
This way you will only get a normal kernel build output with LOTS of modules.
_________________
|
|
| Back to top |
|
|
hjkl
Apprentice
Joined: 22 Apr 2021
Posts: 198
Location: Somewhere in Europe
|
| Posted: Fri Jul 23, 2021 8:08 pm Post subject: |
|
|
| alamahant wrote: | You compiled via genkernel?
I think there is nothing to worry about.
These are normal build output similar to when compiling any package via emerge.
After the build you should have run
if the exit status is 0 all is ok.
Why dont you use
| Code: |
make menuconfig
make
sudo make modules_install
sudo make install
|
without using an intermediary?
This way you will only get a normal kernel build output with LOTS of modules.
|
I found it it was because of a option i set in the kernel that would zero-init any stack variables not explicitly initialized that may be passed by a reference
_________________
Having problems compiling since 2021 |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
