0022-compiler-workaround.patch 1.3 KB

1234567891011121314151617181920212223242526272829303132333435
  1. From 00827741648ebd7d5f98e5f9fd718ad2f7435785 Mon Sep 17 00:00:00 2001
  2. From: Rebecca Chang Swee Fun <rebecca.chang@starfivetech.com>
  3. Date: Thu, 28 Apr 2022 01:04:59 +0000
  4. Subject: [PATCH 22/22] compiler workaround
  5. Signed-off-by: Rebecca Chang Swee Fun <rebecca.chang@starfivetech.com>
  6. ---
  7. build/config/compiler/BUILD.gn | 4 +++-
  8. 1 file changed, 3 insertions(+), 1 deletion(-)
  9. diff --git a/build/config/compiler/BUILD.gn b/build/config/compiler/BUILD.gn
  10. index 429943e426ef3..0ccc0035434f3 100644
  11. --- a/build/config/compiler/BUILD.gn
  12. +++ b/build/config/compiler/BUILD.gn
  13. @@ -1154,6 +1154,7 @@ config("compiler_cpu_abi") {
  14. }
  15. } else if (current_cpu == "riscv64") {
  16. cflags += [
  17. + "--target=riscv64-linux-gnu",
  18. "-m64",
  19. "-march=rv64gc",
  20. "-mabi=lp64d",
  21. @@ -1627,7 +1628,8 @@ config("chromium_code") {
  22. if (!is_debug && !using_sanitizer && current_cpu != "s390x" &&
  23. current_cpu != "s390" && current_cpu != "ppc64" &&
  24. - current_cpu != "mips" && current_cpu != "mips64") {
  25. + current_cpu != "mips" && current_cpu != "mips64" &&
  26. + current_cpu != "riscv64") {
  27. # Non-chromium code is not guaranteed to compile cleanly with
  28. # _FORTIFY_SOURCE. Also, fortified build may fail when optimizations are
  29. # disabled, so only do that for Release build.
  30. --
  31. 2.25.1