News for hackers. Stuff that matters.

A comment on BarraCUDA Open-source CUDA compiler targeting AMD GPUs. Parent comment

Re:BarraCUDA Open-source CUDA compiler targeting AMD GPUs by lelanthran on Wednesday February 18, 2026 @10:16AM (#47061890)
> I guess this is the difference, I expect the commit to represent a somewhat working version,

On a solo project I do the opposite: I make sure there is an error where I stopped last. Typically I put in in a call to the function that is needed next so i get a linker error.

6 months later when I go back to the project that link error tells me all I need to know about what comes next

[ Parent | on HN ]
Re:BarraCUDA Open-source CUDA compiler targeting AMD GPUs by embedding-shape on Wednesday February 18, 2026 @11:10AM (#47062556)
How does that work out if you want to use `git bisect` to find regressions or similar things?
[ Parent | on HN ]
Re:BarraCUDA Open-source CUDA compiler targeting AMD GPUs by lelanthran on Wednesday February 18, 2026 @01:10PM (#47064124)
I dont do bisects on each individual branch. I'll bisect on master instead and find the offending merge.

From that point bisect is not needed.

[ Parent | on HN ]