[libc-commits] [libc] [libc][search] implement posix `lfind` function (PR #114692)

[Nick Desaulniers via libc-commits]

================
@@ -0,0 +1,41 @@
+//===-- Implementation of lfind   -------------------------------*- C++ -*-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
+//
+//===----------------------------------------------------------------------===//
+
+#include "src/search/lfind.h"
+#include "src/__support/CPP/cstddef.h" // cpp::byte
+#include "src/__support/common.h"
+#include "src/__support/macros/config.h"
+#include "src/__support/memory_size.h"
+
+namespace LIBC_NAMESPACE_DECL {
+LLVM_LIBC_FUNCTION(void *, lfind,
+                   (const void *key, const void *base, size_t *nmemb,
+                    size_t size, int (*compar)(const void *, const void *))) {
+  if (key == nullptr || base == nullptr || nmemb == nullptr ||
+      compar == nullptr)
+    return nullptr;
+
+  size_t byte_len = 0;
+  if (internal::mul_overflow(*nmemb, size, &byte_len))
+    return nullptr;
+
+  const cpp::byte *next = reinterpret_cast<const cpp::byte *>(base);
+  const cpp::byte *end = next + byte_len;
+  while (next < end) {
+    if (compar(key, next) == 0) {
+      // According to IEEE Std 1003.1-2024 we are expected to accept a const
+      // reference to base, but return a non-const reference to the element it
+      // contains.
----------------
nickdesaulniers wrote:

ah, sorry, I was mixing up the pointer being const vs the pointed to type.  I don't feel strongly about `cpp::byte` vs `char`.

https://github.com/llvm/llvm-project/pull/114692