#include <vir/simd.h>
#include <vir/simd_benchmarking.h>

#include <ranges>
#include <string_view>

#include "benchmark.h"

std::array<std::string_view, 64> test_strings = {
    "Returns the number of elements in the range [first, last) satisfying specific "
    "criteria.",
    "1) counts the elements that are equal to value.",
    "3) counts elements for which predicate p returns true.",
    "2,4) Same as (1,3), but uses r as the source range, as if using ranges::begin(r) as "
    "first and ranges::end(r) as last.",
    "The function-like entities described on this page are niebloids, that is:",
    "",
    "Explicit template argument lists cannot be specified when calling any of them.\n"
    "None of them are visible to argument-dependent lookup.\n"
    "When any of them are found by normal unqualified lookup as the name to the left of "
    "the function-call operator, argument-dependent lookup is inhibited.\n",
    "In practice, they may be implemented as function objects, or with special compiler "
    "extensions.",
    "Parameters\n"
    "first, last   -   the range of elements to examine\n"
    "r   -   the range of the elements to examine\n"
    "value   -   the value to search for\n"
    "pred  -   predicate to apply to the projected elements\n"
    "proj  -   projection to apply to the elements\n",
    "Return value",
    "Number of elements satisfying the condition.",
    "Complexity",
    "Exactly last - first comparisons and projection.",
    "For the number of elements in the range without any additional criteria, see "
    "std::ranges::distance. ]",
    "The C++ source file is processed by the compiler as if the following phases take "
    "place, in this exact order:",
    "Phase 1",
    "1) The individual bytes of the source code file are mapped (in "
    "implementation-defined manner) to the characters of the basic source character set. "
    "In particular, OS-dependent end-of-line indicators are replaced by newline "
    "characters.",
    "2) The set of source file characters accepted is implementation-defined (since "
    "C++11). Any source file character that cannot be mapped to a character in the basic "
    "source character set is replaced by its universal character name (escaped with "
    "\\u or \\U) or by some implementation-defined form that is handled equivalently.",
    "3) Trigraph sequences are replaced by corresponding single-character "
    "representations.",
    "(until C++17)",
    "(until C++23)",
    "Input files that are a sequence of UTF-8 code units (UTF-8 files) are guaranteed to "
    "be supported. The set of other supported kinds of input files is "
    "implementation-defined. If the set is non-empty, the kind of an input file is "
    "determined in an implementation-defined manner that includes a means of designating "
    "input files as UTF-8 files, independent of their content (recognizing the byte "
    "order mark is not sufficient).",
    "If an input file is determined to be a UTF-8 file, then it shall be a well-formed "
    "UTF-8 code unit sequence and it is decoded to produce a sequence of Unicode scalar "
    "values. A sequence of translation character set elements is then formed by mapping "
    "each Unicode scalar value to the corresponding translation character set element. "
    "In the resulting sequence, each pair of characters in the input sequence consisting "
    "of carriage return (U+000D) followed by line feed (U+000A), as well as each "
    "carriage return (U+000D) not immediately followed by a line feed (U+000A), is "
    "replaced by a single new-line character.",
    "For any other kind of input file supported by the implementation, characters are "
    "mapped (in implementation-defined manner) to a sequence of translation character "
    "set elements. In particular, OS-dependent end-of-line indicators are replaced by "
    "new-line characters.",
    "(since C++23)",
    "Phase 2",
    "1) If the first translation character is byte order mark (U+FEFF), it is deleted. "
    "(since C++23) Whenever backslash appears at the end of a line (immediately followed "
    "by zero or more whitespace characters other than new-line followed by (since C++23) "
    "the newline character), these characters are deleted, combining two physical source "
    "lines into one logical source line. This is a single-pass operation; a line ending "
    "in two backslashes followed by an empty line does not combine three lines into one. "
    "If a universal character name is formed outside raw string literals (since C++11) "
    "in this phase, the behavior is undefined.",
    "2) If a non-empty source file does not end with a newline character after this step "
    "(whether it had no newline originally, or it ended with a newline immediately "
    "preceded by a backslash), a terminating newline character is added.",
    "Unlike static_cast, but like const_cast, the reinterpret_cast expression does not "
    "compile to any CPU instructions (except when converting between integers and "
    "pointers or on obscure architectures where pointer representation depends on its "
    "type). It is purely a compile-time directive which instructs the compiler to treat "
    "expression as if it had the type new-type.",
    "Only the following conversions can be done with reinterpret_cast, except when such "
    "conversions would cast away constness or volatility.",
    "1) An expression of integral, enumeration, pointer, or pointer-to-member type can "
    "be converted to its own type. The resulting value is the same as the value of "
    "expression.",
    "2) A pointer can be converted to any integral type large enough to hold all values "
    "of its type (e.g. to std::uintptr_t)",
    "3) A value of any integral or enumeration type can be converted to a pointer type. "
    "A pointer converted to an integer of sufficient size and back to the same pointer "
    "type is guaranteed to have its original value, otherwise the resulting pointer "
    "cannot be dereferenced safely (the round-trip conversion in the opposite direction "
    "is not guaranteed; the same pointer may have multiple integer representations) The "
    "null pointer constant NULL or integer zero is not guaranteed to yield the null "
    "pointer value of the target type; static_cast or implicit conversion should be used "
    "for this purpose.",
    "4) Any value of type std::nullptr_t, including nullptr can be converted to any "
    "integral type as if it were (void*)0, but no value, not even nullptr can be "
    "converted to std::nullptr_t: static_cast should be used for that purpose.",
    "(since C++11)",
    "5) Any object pointer type T1* can be converted to another object pointer type cv "
    "T2*. This is exactly equivalent to static_cast<cv T2*>(static_cast<cv "
    "void*>(expression)) (which implies that if T2's alignment requirement is not "
    "stricter than T1's, the value of the pointer does not change and conversion of the "
    "resulting pointer back to its original type yields the original value). In any "
    "case, the resulting pointer may only be dereferenced safely if allowed by the type "
    "aliasing rules (see below)",
    "6) An lvalue (until C++11)glvalue (since C++11) expression of type T1 can be "
    "converted to reference to another type T2. The result is that of "
    "*reinterpret_cast<T2*>(p), where p is a pointer of type “pointer to T1” to the "
    "object designated by expression. No temporary is created, no copy is made, no "
    "constructors or conversion functions are called. The resulting reference can only "
    "be accessed safely if allowed by the type aliasing rules (see below)",
    "7) Any pointer to function can be converted to a pointer to a different function "
    "type. Calling the function through a pointer to a different function type is "
    "undefined, but converting such pointer back to pointer to the original function "
    "type yields the pointer to the original function.",
    "8) On some implementations (in particular, on any POSIX compatible system as "
    "required by dlsym), a function pointer can be converted to void* or any other "
    "object pointer, or vice versa. If the implementation supports conversion in both "
    "directions, conversion to the original type yields the original value, otherwise "
    "the resulting pointer cannot be dereferenced or called safely.",
    "9) The null pointer value of any pointer type can be converted to any other pointer "
    "type, resulting in the null pointer value of that type. Note that the null pointer "
    "constant nullptr or any other value of type std::nullptr_t cannot be converted to a "
    "pointer with reinterpret_cast: implicit conversion or static_cast should be used "
    "for this purpose.",
    "10) A pointer to member function can be converted to pointer to a different member "
    "function of a different type. Conversion back to the original type yields the "
    "original value, otherwise the resulting pointer cannot be used safely.",
    "11) A pointer to member object of some class T1 can be converted to a pointer to "
    "another member object of another class T2. If T2's alignment is not stricter than "
    "T1's, conversion back to the original type T1 yields the original value, otherwise "
    "the resulting pointer cannot be used safely.",
    "Many compilers issue \"strict aliasing\" warnings in such cases, even though "
    "technically such constructs run afoul of something other than the paragraph "
    "commonly known as the \"strict aliasing rule\".",
    "The purpose of strict aliasing and related rules is to enable type-based alias "
    "analysis, which would be decimated if a program can validly create a situation "
    "where two pointers to unrelated types (e.g., an int* and a float*) could "
    "simultaneously exist and both can be used to load or store the same memory (see "
    "this email on SG12 reflector). Thus, any technique that is seemingly capable of "
    "creating such a situation necessarily invokes undefined behavior.",
    "When it is needed to interpret the bytes of an object as a value of a different "
    "type, std::memcpy or std::bit_cast (since C++20) can be used: ",
    "If the implementation provides std::intptr_t and/or std::uintptr_t, then a cast "
    "from a pointer to an object type or cv void to these types is always well-defined. "
    "However, this is not guaranteed for a function pointer.",
    "(since C++11)",
    "The paragraph defining the strict aliasing rule in the standard used to contain two "
    "additional bullets partially inherited from C:",
    "AliasedType is an aggregate type or a union type which holds one of the "
    "aforementioned types as an element or non-static member (including, recursively, "
    "elements of subaggregates and non-static data members of the contained unions).",
    "AliasedType is a (possibly cv-qualified) base class of DynamicType.",
    "These bullets describe situations that cannot arise in C++ and therefore are "
    "omitted from the discussion above. In C, aggregate copy and assignment access the "
    "aggregate object as a whole. But in C++ such actions are always performed through a "
    "member function call, which accesses the individual subobjects rather than the "
    "entire object (or, in the case of unions, copies the object representation, i.e., "
    "via unsigned char). These bullets were eventually removed via CWG issue 2051. ",
    "std::memcpy may be used to implicitly create objects in the destination buffer.",
    "std::memcpy is meant to be the fastest library routine for memory-to-memory copy. "
    "It is usually more efficient than std::strcpy, which must scan the data it copies "
    "or std::memmove, which must take precautions to handle overlapping inputs.",
    "Several C++ compilers transform suitable memory-copying loops to std::memcpy calls.",
    "Where strict aliasing prohibits examining the same memory as values of two "
    "different types, std::memcpy may be used to convert the values.",
    "If Derived is polymorphic, such pointer may be used to make virtual function calls.",
    "Certain addition, subtraction, increment, and decrement operators are defined for "
    "pointers to elements of arrays: such pointers satisfy the "
    "LegacyRandomAccessIterator requirements and allow the C++ library algorithms to "
    "work with raw arrays.",
    "Comparison operators are defined for pointers to objects in some situations: two "
    "pointers that represent the same address compare equal, two null pointer values "
    "compare equal, pointers to elements of the same array compare the same as the array "
    "indexes of those elements, and pointers to non-static data members with the same "
    "member access compare in order of declaration of those members.",
    "Many implementations also provide strict total ordering of pointers of random "
    "origin, e.g. if they are implemented as addresses within continuous virtual address "
    "space. Those implementations that do not (e.g. where not all bits of the pointer "
    "are part of a memory address and have to be ignored for comparison, or an "
    "additional calculation is required or otherwise pointer and integer is not a 1 to 1 "
    "relationship), provide a specialization of std::less for pointers that has that "
    "guarantee. This makes it possible to use all pointers of random origin as keys in "
    "standard associative containers such as std::set or std::map.",
    "If the original pointer is pointing to a base class subobject within an object of "
    "some polymorphic type, dynamic_cast may be used to obtain a void* that is pointing "
    "at the complete object of the most derived type.",
    "Pointers to void have the same size, representation and alignment as pointers to "
    "char.",
    "Pointers to void are used to pass objects of unknown type, which is common in C "
    "interfaces: std::malloc returns void*, std::qsort expects a user-provided callback "
    "that accepts two const void* arguments. pthread_create expects a user-provided "
    "callback that accepts and returns void*. In all cases, it is the caller's "
    "responsibility to cast the pointer to the correct type before use.",
    "Pointers to functions",
};

void bench_ranges_count(benchmark::State &state) {
  for (auto _ : state) {
    for (auto s : test_strings) {
      vir::fake_read(std::ranges::count(s, ' '));
    }
  }
}

BENCHMARK(bench_ranges_count);