search for: codeql

Displaying 7 results from an estimated 7 matches for "codeql".

2025 Apr 08
1
NUT testing for v2.8.3 (hopefully imminent)
I'm starting down the path of testing. There are commits in the rc tag that are not on master: $ git log --oneline ..v2.8.3-rc1 3d286fb1b (tag: v2.8.3-rc1, jimklimov/pre-283-2) appveyor.yml: handle also FTY and fightwarn branches 4e92275c1 .github/workflows/codeql.yml: handle also FTY and fightwarn branches 504706d45 Makefile.am: nut-scanner does directly depend on clients after all 051b49d9f Revert "Revert "NEWS.adoc, UPGRADING.adoc, docs/docinfo.xml.in: finalize text before NUT v2.8.3 release"" 70faea2af Revert "tools/gitlog2...
2025 Apr 08
1
NUT testing for v2.8.3 (hopefully imminent)
I'm starting down the path of testing. There are commits in the rc tag that are not on master: $ git log --oneline ..v2.8.3-rc1 3d286fb1b (tag: v2.8.3-rc1, jimklimov/pre-283-2) appveyor.yml: handle also FTY and fightwarn branches 4e92275c1 .github/workflows/codeql.yml: handle also FTY and fightwarn branches 504706d45 Makefile.am: nut-scanner does directly depend on clients after all 051b49d9f Revert "Revert "NEWS.adoc, UPGRADING.adoc, docs/docinfo.xml.in: finalize text before NUT v2.8.3 release"" 70faea2af Revert "tools/gitlog2...
2025 Apr 08
2
NUT testing for v2.8.3 (hopefully imminent)
...starting down the path of testing. > > > There are commits in the rc tag that are not on master: > > $ git log --oneline ..v2.8.3-rc1 > 3d286fb1b (tag: v2.8.3-rc1, jimklimov/pre-283-2) appveyor.yml: handle > also FTY and fightwarn branches > 4e92275c1 .github/workflows/codeql.yml: handle also FTY and fightwarn > branches > 504706d45 Makefile.am: nut-scanner does directly depend on clients after > all > 051b49d9f Revert "Revert "NEWS.adoc, UPGRADING.adoc, docs/docinfo.xml.in: > finalize text before NUT v2.8.3 release"" > 70faea...
2025 Apr 08
2
NUT testing for v2.8.3 (hopefully imminent)
...starting down the path of testing. > > > There are commits in the rc tag that are not on master: > > $ git log --oneline ..v2.8.3-rc1 > 3d286fb1b (tag: v2.8.3-rc1, jimklimov/pre-283-2) appveyor.yml: handle > also FTY and fightwarn branches > 4e92275c1 .github/workflows/codeql.yml: handle also FTY and fightwarn > branches > 504706d45 Makefile.am: nut-scanner does directly depend on clients after > all > 051b49d9f Revert "Revert "NEWS.adoc, UPGRADING.adoc, docs/docinfo.xml.in: > finalize text before NUT v2.8.3 release"" > 70faea...
2025 Apr 08
1
NUT testing for v2.8.3 (hopefully imminent)
So, NUT v2.8.3-rc1 is out. I first thought it was the release, but some CI runs convinced me otherwise, so there would be a bit of back and forth on the master branch as some recipes get fixed. Apparently, some parallel runs stepped onto each other's toes sometimes, but coinciding the wrong way just once in a few hundred builds. Hopefully I found why and will re-publish in a few hours. Jim
2025 Apr 08
1
NUT testing for v2.8.3 (hopefully imminent)
So, NUT v2.8.3-rc1 is out. I first thought it was the release, but some CI runs convinced me otherwise, so there would be a bit of back and forth on the master branch as some recipes get fixed. Apparently, some parallel runs stepped onto each other's toes sometimes, but coinciding the wrong way just once in a few hundred builds. Hopefully I found why and will re-publish in a few hours. Jim
2020 Jan 28
3
Where does LTO remove unused functions?
Hi! LLVM newbie here, I was mainly working on the frontend so far. We had a small hackathon project idea to piggyback on LTO to detect dead code (unused functions). The basic idea is to compile the code for every target and dump the removed functions. Intersect the function symbol names for each target and those functions should be safe to remove from the source code (unless there were some