[llvm-bugs] [Bug 34588] New: ARM's clear_cache should not call abort

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=34588

            Bug ID: 34588
           Summary: ARM's clear_cache should not call abort
           Product: compiler-rt
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: compiler-rt
          Assignee: manojgupta at google.com
          Reporter: manojgupta at google.com
                CC: compnerd at compnerd.org, llozano at chromium.org,
                    llvm-bugs at lists.llvm.org, llvm-bugzilla at jfbastien.com,
                    renato.golin at linaro.org, srhines at google.com

clear_cache for ARM is calling abort() when start address is not a NULL
pointer. clear_cache documentation in libgcc does not specify any aborting
behavior. Libgcc implementation does not do abort either.

Calling abort for a non-null start address does not make any sense either and
libgcc docs do not say that the start argument has to be NULL.

This issue was discovered when compiler-rt was enabled for ChromeOS and NaCl
failed since it was making calls to __builtin___clear_cache()
 (https://bugs.chromium.org/p/chromium/issues/detail?id=761103).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20170913/d334b034/attachment.html>