[all-commits] [llvm/llvm-project] 322d01: [clang-tidy] Do not flag strerror in concurrency-m...

[Carlos Galvez via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 322d0197f5c5d4cf3a6bb2d86a0112788fd6c529
      https://github.com/llvm/llvm-project/commit/322d0197f5c5d4cf3a6bb2d86a0112788fd6c529
  Author: Carlos Galvez <carlosgalvezp at gmail.com>
  Date:   2025-05-19 (Mon, 19 May 2025)

  Changed paths:
    M clang-tools-extra/clang-tidy/concurrency/MtUnsafeCheck.cpp
    M clang-tools-extra/docs/ReleaseNotes.rst
    M clang-tools-extra/test/clang-tidy/checkers/concurrency/mt-unsafe-glibc.cpp

  Log Message:
  -----------
  [clang-tidy] Do not flag strerror in concurrency-mt-unsafe (#140520)

The docs of the check state:

> Glibc’s list is compiled from GNU web documentation with a search for
MT-Safe tag

And strerror fulfills exactly that:
https://www.gnu.org/software/libc/manual/html_node/Error-Messages.html

> Function: char * strerror (int errnum)
> Preliminary: | MT-Safe | AS-Unsafe heap i18n | AC-Unsafe mem | See
POSIX Safety Concepts.

So concurrency-mt-unsafe should not flag it.

Fixes #140515

---------

Co-authored-by: Carlos Gálvez <carlos.galvez at zenseact.com>
Co-authored-by: EugeneZelenko <eugene.zelenko at gmail.com>



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications