[lvaroqui]

Restore upstream's trailing whitespace on the 496 lines (10 files) where it was the only difference from upstream VALGRIND_3_26_0.

Earlier upstream merges (3.24.0 and 3.26.0) stripped it from upstream lines in configure.ac, NEWS, the syswrap and debuginfo sources, and the untouched parts of the callgrind files we modify. Any upstream edit next to one of those lines then conflicts at the next merge: in a trial merge of 3.27.1, 6 of the 7 conflict hunks were only this.

The change is whitespace-only: git diff --ignore-space-at-eol over the commit is empty, and every touched file now differs from VALGRIND_3_26_0 only by our real changes.

PS: yes this is so cursed 🤣

Refs COD-3818

[greptile-apps]

Confidence Score: 5/5

[Low impact] The PR appears safe to merge; no actionable defects were established.

Summary

Restores upstream trailing whitespace on 496 lines across 10 files to reduce conflicts in future upstream merges.

• Upstream source lines keep their original trailing spaces.

_{Reviews (1) · Last reviewed commit: "style: restore upstream trailing whitesp..." · Reviewed by Greptile}

[codspeed]

Merging this PR will not alter performance

✅ 84 untouched benchmarks
⏩ 60 skipped benchmarks¹

---

_{Comparing chore/restore-upstream-trailing-whitespace (a9fdff3) with master (47784c0)}

Footnotes

1. 60 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[not-matthias]

Great work!! 🚀 🔥