helloadhavan/github_issues huggingface dataset:
Repository: ggml-org/llama.cpp
Pull request: vulkan: set cmake minimum and project name in vulkan-shaders

I forced the CMAKE_CROSSCOMPILING path in ggml-vulkan/CMakeLists.txt and was able to build it with these minor changes. Without them, the errors were:

```
3>CMake Warning (dev) in CMakeLists.txt:
3>  No project() command is present.  The top-level CMakeLists.txt file must
3>  contain a literal, direct call to the project() command.  Add a line of
3>  code such as
3>
3>    project(ProjectName)
3>
3>  near the top of the file, but after cmake_minimum_required().
3>
3>  CMake is pretending there is a "project(Project)" command on the first
3>  line.
3>This warning is for project developers.  Use -Wno-dev to suppress it.
3>
3>CMake Warning (dev) in CMakeLists.txt:
3>  cmake_minimum_required() should be called prior to this top-level project()
3>  call.  Please see the cmake-commands(7) manual for usage documentation of
3>  both commands.
3>This warning is for project developers.  Use -Wno-dev to suppress it.
3>
3>-- Selecting Windows SDK version 10.0.22621.0 to target Windows 10.0.22631.
3>CMake Error in CMakeLists.txt:
3>  No cmake_minimum_required command is present.  A line of code such as
3>
3>    cmake_minimum_required(VERSION 4.0)
3>
3>  should be added at the top of the file.  The version specified may be lower
3>  if you wish to support older CMake versions for this project.  For more
3>  information run "cmake --help-policy CMP0000".
3>
3>
3>-- Configuring incomplete, errors occurred!
```

I did this experiment with cmake 4.0.0. I didn't get these warnings/errors with the normal build, but I guess they're required when vulkan-shaders-gen is treated as an external project?

This also makes me wonder whether we really need a separate path for cross compiles, or if we could force normal builds down the ExternalProject_Add path. But I didn't attempt to do that in this change.

Changed files:
filename: ggml/src/ggml-vulkan/vulkan-shaders/CMakeLists.txt
patch: @@ -1,3 +1,6 @@
+cmake_minimum_required(VERSION 3.19)
+project("vulkan-shaders-gen" C CXX)
+
 find_package (Threads REQUIRED)
 
 if (GGML_VULKAN_COOPMAT_GLSLC_SUPPORT)
Repository: denoland/deno
Pull request: feat(lsp): respect editor indentation options

Closes #23257. Respects and prioritizes the indentation options selected on the VSCode status bar.

Changed files:
filename: cli/lsp/language_server.rs
patch: @@ -1331,12 +1331,14 @@ impl Inner {
 
     // spawn a blocking task to allow doing other work while this is occurring
     let text_edits = deno_core::unsync::spawn_blocking({
-      let fmt_options = self
+      let mut fmt_options = self
         .config
         .tree
         .fmt_options_for_specifier(&specifier)
         .options
         .clone();
+      fmt_options.use_tabs = Some(!params.options.insert_spaces);
+      fmt_options.indent_width = Some(params.options.tab_size as u8);
       let document = document.clone();
       move || {
         let format_result = match document.maybe_parsed_source() {

filename: tests/integration/lsp_tests.rs
patch: @@ -9765,13 +9765,13 @@ fn lsp_format_json() {
   let res = client.write_request(
     "textDocument/formatting",
     json!({
-        "textDocument": {
-          "uri": json_file.uri(),
-        },
-        "options": {
-          "tabSize": 2,
-          "insertSpaces": true
-        }
+      "textDocument": {
+        "uri": json_file.uri(),
+      },
+      "options": {
+        "tabSize": 2,
+        "insertSpaces": true
+      }
     }),
   );
 
@@ -9802,6 +9802,67 @@ fn lsp_format_json() {
   client.shutdown();
 }
 
+#[test]
+fn lsp_format_editor_options() {
+  let context = TestContextBuilder::new().use_temp_cwd().build();
+  let temp_dir = context.temp_dir();
+  let file = source_file(
+    temp_dir.path().join("file.ts"),
+    "if (true) {\n  console.log();\n}\n",
+  );
+  let mut client = context.new_lsp_command().build();
+  client.initialize_default();
+  let res = client.write_request(
+    "textDocument/formatting",
+    json!({
+      "textDocument": {
+        "uri": file.uri(),
+      },
+      "options": {
+        "tabSize": 4,
+        "insertSpaces": true,
+      },
+    }),
+  );
+  assert_eq!(
+    res,
+    json!([
+      {
+        "range": {
+          "start": { "line": 1, "character": 0 },
+          "end": { "line": 1, "character": 0 },
+        },
+        "newText": "  ",
+      },
+    ])
+  );
+  let res = client.write_request(
+    "textDocument/formatting",
+    json!({
+      "textDocument": {
+        "uri": file.uri(),
+      },
+      "options": {
+        "tabSize": 2,
+        "insertSpaces": false,
+      },
+    }),
+  );
+  assert_eq!(
+    res,
+    json!([
+      {
+        "range": {
+          "start": { "line": 1, "character": 0 },
+          "end": { "line": 1, "character": 2 },
+        },
+        "newText": "\t",
+      },
+    ])
+  );
+  client.shutdown();
+}
+
 #[test]
 fn lsp_json_no_diagnostics() {
   let context = TestContextBuilder::new().use_temp_cwd().build();
@@ -9964,7 +10025,7 @@ fn lsp_format_with_config() {
       },
       "options": {
         "tabSize": 2,
-        "insertSpaces": true
+        "insertSpaces": false
       }
     }),
   );
Repository: denoland/deno
Pull request: build: fix 'deno_core' PR title lint


Changed files:
filename: tools/verify_pr_title.js
patch: @@ -8,8 +8,8 @@ if (prTitle == null) {
 console.log("PR title:", prTitle);
 
 if (
-  prTitle.startsWith("chore:") && prTitle.contains("deno_core") &&
-  (prTitle.contains("upgrade") || prTitle.contains("update"))
+  prTitle.startsWith("chore:") && prTitle.includes("deno_core") &&
+  (prTitle.includes("upgrade") || prTitle.includes("update"))
 ) {
   console.error([
     "Please categorize this deno_core upgrade as a 'feat:', 'fix:' or a ",
Repository: facebook/react
Pull request: DevTools: Add missing param to fetchFromPage()

Follow up for comment left on #22285 after merge.

Changed files:
filename: packages/react-devtools-extensions/src/main.js
patch: @@ -258,7 +258,7 @@ function createPanelIfReactLoaded() {
                       }
 
                       // Edge case where getContent() returned null; fall back to fetch.
-                      fetchFromPage(url, resolve);
+                      fetchFromPage(url, resolve, reject);
                     }
                   });
 
@@ -273,7 +273,7 @@ function createPanelIfReactLoaded() {
               }
 
               // No matching URL found; fall back to fetch.
-              fetchFromPage(url, resolve);
+              fetchFromPage(url, resolve, reject);
             });
           };
Repository: ggml-org/llama.cpp
Pull request: CUDA: Prefer vector flash decoding kernel for Gemma models

Vector flash decoding kernel was not being picked for models with head dimension 256. Gemma models are in this category. Removing this limit improves e2e performance by up to 12% in gen phase throughput for Gemma models.

**Performance:**

RTX 4090, CUDA 12.8, Master vs PR

  | ISL | OSL | Master: Gen phase tok/sec | PR: Gen phase tok/sec | Speed-up
-- | -- | -- | -- | -- | --
gemma3 1B Q4_K - Medium | 10 | 200 | 318.6111 | 333.6684 | 1.047259
  | 100 | 200 | 309.473 | 328.0762 | 1.060113
  | 1000 | 200 | 284.6962 | 319.3516 | 1.121728
  | 10000 | 200 | 183.7296 | 206.1121 | 1.121823
  |   |   |   |   |  
gemma3 4B Q4_K - Medium |   |   |   |   |  
  | 10 | 200 | 175.7797 | 184.4036 | 1.049061
  | 100 | 200 | 174.9861 | 181.8483 | 1.039215
  | 1000 | 200 | 165.9151 | 175.7443 | 1.059242
  | 10000 | 200 | 120.0141 | 126.6009 | 1.054884
  |   |   |   |   |  
gemma3 12B Q4_K - Medium |   |   |   |   |  
  | 10 | 200 | 83.11534 | 85.4468 | 1.028051
  | 100 | 200 | 82.62634 | 84.6703 | 1.024737
  | 1000 | 200 | 80.07223 | 81.96644 | 1.023656
  | 10000 | 200 | 56.99771 | 59.67587 | 1.046987


Changed files:
filename: ggml/src/ggml-cuda/fattn.cu
patch: @@ -299,7 +299,7 @@ void ggml_cuda_flash_attn_ext(ggml_backend_cuda_context & ctx, ggml_tensor * dst
     const bool gqa_opt_applies = ((Q->ne[2] / K->ne[2]) % 2 == 0) && mask; // The mma-based kernels have GQA-specific optimizations
     const bool mma_needs_data_conversion = K->type != GGML_TYPE_F16 || V->type != GGML_TYPE_F16;
     const bool mma_faster_for_bs1 = new_mma_available(cc) && gqa_opt_applies && cc < GGML_CUDA_CC_ADA_LOVELACE && !mma_needs_data_conversion;
-    const bool can_use_vector_kernel = (Q->ne[0] % (2*warp_size) == 0) && (prec == GGML_PREC_DEFAULT || Q->ne[0] <= 128);
+    const bool can_use_vector_kernel = Q->ne[0] % (2*warp_size) == 0;
     if (Q->ne[1] == 1 && can_use_vector_kernel && !mma_faster_for_bs1) {
         if (prec == GGML_PREC_DEFAULT) {
             ggml_cuda_flash_attn_ext_vec_f16(ctx, dst);
Repository: vercel/next.js
Pull request: fix: flaky test detection needs to use new turbopack flag

As of #77894, there's a new way to indicate Turbopack should run, which breaks flaky tests detection with Turbopack. This swaps out the flag to unblock my downstack PR.

Changed files:
filename: scripts/test-new-tests.mjs
patch: @@ -151,7 +151,7 @@ async function main() {
           ...process.env,
           NEXT_TEST_MODE: testMode,
           NEXT_TEST_VERSION: nextTestVersion,
-          TURBOPACK: '1',
+          IS_TURBOPACK_TEST: '1',
           TURBOPACK_BUILD: testMode === 'start' ? '1' : undefined,
           NEXT_EXTERNAL_TESTS_FILTERS:
             testMode === 'dev'
Repository: huggingface/transformers
Pull request: Fix 4090/ada not detected as having FP8 support

# What does this PR do?

FIX 4090/Ada not detected as having valid FP8 hw support. 

Did a simple layer/module inference test with DeepSeek V3 0324 using GPTQModel and there is no issue with Transformer inference on 4090 at the layer/module level. 4090 does not have the memory to run a full all-layer generation. 

## Before submitting
- [ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
- [x] Did you read the [contributor guideline](https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md#create-a-pull-request),
      Pull Request section?
- [ ] Was this discussed/approved via a Github issue or the [forum](https://discuss.huggingface.co/)? Please add a link
      to it if that's the case.
- [ ] Did you make sure to update the documentation with your changes? Here are the
      [documentation guidelines](https://github.com/huggingface/transformers/tree/main/docs), and
      [here are tips on formatting docstrings](https://github.com/huggingface/transformers/tree/main/docs#writing-source-documentation).
- [ ] Did you write any new necessary tests?


## Who can review?

@ArthurZucker @SunMarc @MekkCyber 




Changed files:
filename: src/transformers/quantizers/quantizer_finegrained_fp8.py
patch: @@ -52,9 +52,10 @@ def validate_environment(self, *args, **kwargs):
 
         compute_capability = torch.cuda.get_device_capability()
         major, minor = compute_capability
-        if major < 9:
+        if (major < 8) or (major == 8 and minor < 9):
             raise ValueError(
-                "FP8 quantized models is only supported on GPUs with compute capability >= 9.0 (e.g H100)"
+                "FP8 quantized models is only supported on GPUs with compute capability >= 8.9 (e.g 4090/H100)"
+                f", actual = `{major}.{minor}`"
             )
 
         device_map = kwargs.get("device_map", None)
Repository: facebook/react
Pull request: [DevTools] Fix `react-devtools-extension` build error and `react-devtools-inline`'s `package.json`

This PR includes two bug fixes:
1. `react-devtools-extension` cannot import from `react-devtools-inline`. It should only be importing shared code from `react-devtools-shared`. Fix this by importing the `react-devtools-shared` version of `hookNames`.
2. Add `hookNames.js` as an file to be included when `react-devtools-inline` is installed as a dependency.

Tested these bug fixes by building the extension and the test shell and verifying named hooks works as expected.

Changed files:
filename: packages/react-devtools-extensions/src/main.js
patch: @@ -289,7 +289,7 @@ function createPanelIfReactLoaded() {
 
         // TODO (Webpack 5) Hopefully we can remove this prop after the Webpack 5 migration.
         const hookNamesModuleLoaderFunction = () =>
-          import('react-devtools-inline/hookNames');
+          import('react-devtools-shared/src/hooks/parseHookNames');
 
         root = createRoot(document.createElement('div'));
 

filename: packages/react-devtools-inline/package.json
patch: @@ -13,7 +13,8 @@
     "dist",
     "backend.js",
     "build-info.json",
-    "frontend.js"
+    "frontend.js",
+    "hookNames.js"
   ],
   "scripts": {
     "build": "cross-env NODE_ENV=production webpack --config webpack.config.js",
Repository: ggml-org/llama.cpp
Pull request: Use string_view::find() to search for tokenization to speed up

The old implementation using `std::string::find()` consumes a lot of time if the string is very long, because it searches beyond the fragment range, looking up for tokens after the fragment end (and later drop the match result if it is beyond the range).

_O(n)_ wasted.

**Furthermore, a long string produces more fragments and for each fragment, then a token is searched again and again in the fragments**, i.e. It searches within `[offset1, end) [offset2, end) [offset3, end) ...` where _offsetn_ is the _nth_ of the fragments.

So actually _O(n^2)_ wasted.

Hope this pic helps understand the issue more easily.
![image](https://github.com/user-attachments/assets/5fa1fd5d-0ac7-4355-bc0e-0c6eefd2250d)


By limiting the search area (esp. the end) using `std::string_view::find()`, we can avoid such unnecessary looking up.

This PR contains the minimal code change to solve the performance pitfall, to at least make it work.
Maybe someone should refactor the whole fragment stuff with `std::string_view` for code readability in the future.

Changed files:
filename: src/llama-vocab.cpp
patch: @@ -2221,14 +2221,12 @@ void llama_vocab::impl::tokenizer_st_partition(std::forward_list<fragment_buffer
                     // find the first occurrence of a given special token in this fragment
                     //  passing offset argument only limit the "search area" but match coordinates
                     //  are still relative to the source full raw_text
-                    auto match = raw_text.find(text, raw_text_base_offset);
+                    //  string_view begins at pos 0 for the same reason
+                    auto match = std::string_view(raw_text.data(), raw_text_base_offset + raw_text_base_length).find(text, raw_text_base_offset);
 
                     // no occurrences found, stop processing this fragment for a given special token
                     if (match == std::string::npos) break;
 
-                    // check if match is within bounds of offset <-> length
-                    if (match + text.length() > raw_text_base_offset + raw_text_base_length) break;
-
 #ifdef PRETOKENIZERDEBUG
                     LLAMA_LOG_WARN("FF: (%ld %ld %ld) '%s'\n", raw_text->length(), raw_text_base_offset, raw_text_base_length, raw_text->substr(raw_text_base_offset, raw_text_base_length).c_str());
 #endif
Repository: ggml-org/llama.cpp
Pull request: vulkan: Fix missing cmake logic for dot product extension

This is a missing interaction between #12135 and #12272 

Changed files:
filename: ggml/src/ggml-vulkan/CMakeLists.txt
patch: @@ -64,8 +64,10 @@ if (Vulkan_FOUND)
 
     if (${glslc_error} MATCHES ".*extension not supported: GL_EXT_integer_dot_product.*")
         message(STATUS "GL_EXT_integer_dot_product not supported by glslc")
+        set(GGML_VULKAN_INTEGER_DOT_GLSLC_SUPPORT OFF)
     else()
         message(STATUS "GL_EXT_integer_dot_product supported by glslc")
+        set(GGML_VULKAN_INTEGER_DOT_GLSLC_SUPPORT ON)
         add_compile_definitions(GGML_VULKAN_INTEGER_DOT_GLSLC_SUPPORT)
     endif()
 
@@ -139,6 +141,7 @@ if (Vulkan_FOUND)
                     -DCMAKE_INSTALL_PREFIX=${CMAKE_BINARY_DIR}
                     -DGGML_VULKAN_COOPMAT_GLSLC_SUPPORT=${GGML_VULKAN_COOPMAT_GLSLC_SUPPORT}
                     -DGGML_VULKAN_COOPMAT2_GLSLC_SUPPORT=${GGML_VULKAN_COOPMAT2_GLSLC_SUPPORT}
+                    -DGGML_VULKAN_INTEGER_DOT_GLSLC_SUPPORT=${GGML_VULKAN_INTEGER_DOT_GLSLC_SUPPORT}
             BUILD_COMMAND ${CMAKE_COMMAND} --build .
             INSTALL_COMMAND ${CMAKE_COMMAND} --install .
             INSTALL_DIR ${CMAKE_BINARY_DIR}

filename: ggml/src/ggml-vulkan/vulkan-shaders/CMakeLists.txt
patch: @@ -6,6 +6,9 @@ endif()
 if (GGML_VULKAN_COOPMAT2_GLSLC_SUPPORT)
     add_compile_definitions(GGML_VULKAN_COOPMAT2_GLSLC_SUPPORT)
 endif()
+if (GGML_VULKAN_INTEGER_DOT_GLSLC_SUPPORT)
+    add_compile_definitions(GGML_VULKAN_INTEGER_DOT_GLSLC_SUPPORT)
+endif()
 set(TARGET vulkan-shaders-gen)
 add_executable(${TARGET} vulkan-shaders-gen.cpp)
 install(TARGETS ${TARGET} RUNTIME)
Repository: denoland/deno
Pull request: fix(jupyter): Avoid panicking when `DEBUG` env var is set

Fixes #22050.

It seems very unlikely that a user would be intending to enable deno's internal debug logs by setting the DEBUG env var. If they really want that, they can set `RUST_LOG=debug` instead.

Changed files:
filename: cli/tools/jupyter/mod.rs
patch: @@ -7,7 +7,6 @@ use crate::tools::repl;
 use crate::tools::test::create_single_test_event_channel;
 use crate::tools::test::reporters::PrettyTestReporter;
 use crate::tools::test::TestEventWorkerSender;
-use crate::util::logger;
 use crate::CliFactory;
 use deno_core::anyhow::Context;
 use deno_core::error::generic_error;
@@ -52,11 +51,6 @@ pub async fn kernel(
 
   let connection_filepath = jupyter_flags.conn_file.unwrap();
 
-  // This env var might be set by notebook
-  if std::env::var("DEBUG").is_ok() {
-    logger::init(Some(log::Level::Debug));
-  }
-
   let factory = CliFactory::from_flags(flags)?;
   let cli_options = factory.cli_options();
   let main_module =
Repository: nodejs/node
Pull request: build: update ruff and add `lint-py-fix`

This PR updates `ruff` to 0.6.5, and adds two new makefile targets:
`lint-py-fix`
`lint-py-fix-unsafe`

Changed files:
filename: Makefile
patch: @@ -1536,17 +1536,22 @@ cpplint: lint-cpp
 # Try with '--system' if it fails without; the system may have set '--user'
 lint-py-build:
 	$(info Pip installing ruff on $(shell $(PYTHON) --version)...)
-	$(PYTHON) -m pip install --upgrade --target tools/pip/site-packages ruff==0.5.2 || \
-		$(PYTHON) -m pip install --upgrade --system --target tools/pip/site-packages ruff==0.5.2
+	$(PYTHON) -m pip install --upgrade --target tools/pip/site-packages ruff==0.6.5 || \
+		$(PYTHON) -m pip install --upgrade --system --target tools/pip/site-packages ruff==0.6.5
 
-.PHONY: lint-py
+.PHONY: lint-py lint-py-fix lint-py-fix-unsafe
 ifneq ("","$(wildcard tools/pip/site-packages/ruff)")
 # Lint the Python code with ruff.
 lint-py:
 	$(info Running Python linter...)
 	tools/pip/site-packages/bin/ruff check .
+lint-py-fix:
+	tools/pip/site-packages/bin/ruff check . --fix
+
+lint-py-fix-unsafe:
+	tools/pip/site-packages/bin/ruff check . --fix --unsafe-fixes
 else
-lint-py:
+lint-py lint-py-fix lint-py-fix-unsafe:
 	$(warning Python linting with ruff is not available)
 	$(warning Run 'make lint-py-build')
 endif
@@ -1604,6 +1609,7 @@ lint-clean:
 	$(RM) tools/.*lintstamp
 	$(RM) .eslintcache
 	$(RM) -r tools/eslint/node_modules
+	$(RM) tools/pip/site_packages
 
 HAS_DOCKER ?= $(shell command -v docker > /dev/null 2>&1; [ $$? -eq 0 ] && echo 1 || echo 0)
 

filename: tools/v8-json-to-junit.py
patch: @@ -34,7 +34,7 @@
 import utils
 import signal
 import sys
-import xml.etree.ElementTree as xml
+import xml.etree.ElementTree as ET
 
 def IsExitCodeCrashing(exit_code):
   if utils.IsWindows():
@@ -44,22 +44,22 @@ def IsExitCodeCrashing(exit_code):
 
 class JUnitTestOutput:
   def __init__(self, test_suite_name):
-    self.root = xml.Element("testsuite")
+    self.root = ET.Element("testsuite")
     self.root.attrib["name"] = test_suite_name
 
   def HasRunTest(self, test_name, test_cmd, test_duration, test_failure):
-    test_case_element = xml.Element("testcase")
+    test_case_element = ET.Element("testcase")
     test_case_element.attrib["name"] = test_name
     test_case_element.attrib["cmd"] = test_cmd
     test_case_element.attrib["time"] = str(round(test_duration, 3))
     if test_failure is not None:
-      failure_element = xml.Element("failure")
+      failure_element = ET.Element("failure")
       failure_element.text = test_failure
       test_case_element.append(failure_element)
     self.root.append(test_case_element)
 
   def FinishAndWrite(self, f):
-    xml.ElementTree(self.root).write(f, "UTF-8")
+    ET.ElementTree(self.root).write(f, "UTF-8")
 
 
 def Main():
Repository: ggml-org/llama.cpp
Pull request: SYCL: Set the SYCL_PROGRAM_COMPILE_OPTIONS env variable in the CI

The CPY operation tests occasionally fail on both nvptx and intel targets of the SYCL backend, which stem from using lesser precise instructions. Setting the environment `SYCL_PROGRAM_COMPILE_OPTION` to `-cl-fp32-correctly-rounded-divide-sqrt` resolves this issue. On the nvptx backends, passing `-fno-fast-math` resolves the same. 

This PR adds the environment variables, and conveys the same via the SYCL.md file.

Changed files:
filename: ci/run.sh
patch: @@ -59,6 +59,8 @@ if [ ! -z ${GG_BUILD_SYCL} ]; then
     export ONEAPI_DEVICE_SELECTOR="level_zero:0"
     # Enable sysman for correct memory reporting
     export ZES_ENABLE_SYSMAN=1
+    # to circumvent precision issues on CPY operations
+    export SYCL_PROGRAM_COMPILE_OPTIONS="-cl-fp32-correctly-rounded-divide-sqrt"
     CMAKE_EXTRA="${CMAKE_EXTRA} -DGGML_SYCL=1 -DCMAKE_C_COMPILER=icx -DCMAKE_CXX_COMPILER=icpx -DGGML_SYCL_F16=ON"
 fi
 

filename: docs/backend/SYCL.md
patch: @@ -302,6 +302,10 @@ cmake -B build -DGGML_SYCL=ON -DCMAKE_C_COMPILER=icx -DCMAKE_CXX_COMPILER=icpx -
 cmake --build build --config Release -j -v
 ```
 
+It is possible to come across some precision issues when running tests that stem from using faster
+instructions, which can be circumvented by setting the environment variable `SYCL_PROGRAM_COMPILE_OPTIONS`
+as `-cl-fp32-correctly-rounded-divide-sqrt`
+
 #### Nvidia GPU
 
 The SYCL backend depends on [oneMath](https://github.com/uxlfoundation/oneMath) for Nvidia and AMD devices.
@@ -322,6 +326,9 @@ cmake -B build -DGGML_SYCL=ON -DGGML_SYCL_TARGET=NVIDIA -DGGML_SYCL_DEVICE_ARCH=
 cmake --build build --config Release -j -v
 ```
 
+It is possible to come across some precision issues when running tests that stem from using faster
+instructions, which can be circumvented by passing the `-fno-fast-math` flag to the compiler.
+
 #### AMD GPU
 
 The SYCL backend depends on [oneMath](https://github.com/uxlfoundation/oneMath) for Nvidia and AMD devices.