-
```
Compiling the update master with -O3 on gentoo, I see:
* QA Notice: Package triggers severe warnings which indicate that it
* may exhibit random runtime failures.
* /usr/include/b…
-
```
Compiling the update master with -O3 on gentoo, I see:
* QA Notice: Package triggers severe warnings which indicate that it
* may exhibit random runtime failures.
* /usr/include/b…
-
Not sure why, here's a log: [umockdev.log](https://github.com/InBetweenNames/gentooLTO/files/3369835/umockdev.log)
I suspect it might be an O3 issue, but I can't get my cflag patches to work
-
```
Compiling the update master with -O3 on gentoo, I see:
* QA Notice: Package triggers severe warnings which indicate that it
* may exhibit random runtime failures.
* /usr/include/b…
-
```
Compiling the update master with -O3 on gentoo, I see:
* QA Notice: Package triggers severe warnings which indicate that it
* may exhibit random runtime failures.
* /usr/include/b…
-
Both linux-6.11.3 and linux-6.11.3-gentoo fail to build with clang-19 when CONFIG_DRM_AMD_DC is set to 'y' in the kernel configuration. The Linux kernel builds properly with the same configuration whe…
-
```
Compiling the update master with -O3 on gentoo, I see:
* QA Notice: Package triggers severe warnings which indicate that it
* may exhibit random runtime failures.
* /usr/include/b…
-
```
Compiling the update master with -O3 on gentoo, I see:
* QA Notice: Package triggers severe warnings which indicate that it
* may exhibit random runtime failures.
* /usr/include/b…
-
```
Compiling the update master with -O3 on gentoo, I see:
* QA Notice: Package triggers severe warnings which indicate that it
* may exhibit random runtime failures.
* /usr/include/b…
-
What do you think about optimizing the caching ?
First thing that comes to mind is caching the parsed result instead of caching the raw xml. Second I thought about an optional locking when doing the …