[llvm-bugs] [Bug 43977] New: Access Violation Error when throwing exception with clang-cl, gtest and exception

via llvm-bugs llvm-bugs at lists.llvm.org
Tue Nov 12 05:06:00 PST 2019


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

            Bug ID: 43977
           Summary: Access Violation Error when throwing exception with
                    clang-cl, gtest and exception
           Product: new-bugs
           Version: trunk
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: new bugs
          Assignee: unassignedbugs at nondot.org
          Reporter: feildel at corona-renderer.com
                CC: htmldeveloper at gmail.com, llvm-bugs at lists.llvm.org

Created attachment 22799
  --> https://bugs.llvm.org/attachment.cgi?id=22799&action=edit
Test case

We've hit a very specific bug while running our unit tests compiled with
clang-10. I have been able to isolate the bug in a self contained project
shared as attachments. You can find a rudimentary build script and some
instructions to build an executable that can reproduce the access violation
error.

The test has been reduced as much as possible as far as I could test everything
is needed to reproduce the conditions to create the Access Violation Error.

It seems that the following features use in combination are creating the
situation where clang (or LLVM) generates the wrong code:

- goto
- SSE intrisics
- Forced inlining

I tested again clang-cl build on my machine from git revision
1c616a9266bd829ea8915617ff83244df45a31c8 in repo
https://github.com/llvm/llvm-project.git

Let me know if you need more information.
B. Feildel

-- 
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/20191112/3742e751/attachment-0001.html>


More information about the llvm-bugs mailing list