Hello, everyone.

Instead of a multitude of e-mails, this is one meta-ping for
a bunch of small patches sent by me in the last few weeks.

I'm very new here so let me know if this kind of patch isn't
particularly interesting at the moment. I wouldn't want to
waste your time unnecessarily.

See below a list of patches, its gcc-patches archive link,
and some remarks for each of them.


(1) [PATCH][v2] vtv: Fix Memory Leak and Other Improvements
    https://gcc.gnu.org/pipermail/gcc-patches/2026-July/725973.html
    This V2 was completely rewritten after feedback from Jason
    Merrill. It is just a refactor of two (now three) functions,
    to prevent a memory leak and provide some improvements along,
    which can be read about in the mail above.

(2) [PATCH][V2] middle-end: avoid redundant 'sorry' message.
    https://gcc.gnu.org/pipermail/gcc-patches/2026-July/725331.html
    This also follows feedback from Jason, but very small and clearly
    scoped. Looks like a regression in GCC 16 and trunk.
    It seems no one opened a PR for this yet.

    https://godbolt.org/z/EznWd5zGc

(3) [PATCH][V1] OpenMP: Fix ICE on invalid for loop parsing.
    https://gcc.gnu.org/pipermail/gcc-patches/2026-July/724917.html
    This is to avoid an ICE when invalid openmp related code is compiled.

    Studying the code of commit 53891f18, it seems that a 'return NULL'
    from cp_parser_omp_loop was refactored into another function and did
    not preserve its previous meaning. Might require more serious analysis,
    though.

    Should solve PR libgomp/125691

(4) Re: [Ping][V2][PATCH] doc: Update references to deleted global variables.
    https://gcc.gnu.org/pipermail/gcc-patches/2026-July/722735.html
    This incorporates feedback from Sandra Loosemore and Richard Biener.
    It's a docu update that swaps an old variable name for its current name.

(5) [Ping] [PATCH] doc: Clarify texi2pod behaviour.
    https://gcc.gnu.org/pipermail/gcc-patches/2026-May/717821.html
    This is to replace a FIXME in the internals doc from 2002 with a
    small paragraph.

Have a great week,
Léo

Reply via email to