Linux/ARM: Bus error with -O3 flag of clang/llvm-3.6 while running unit-test of .NET Core

[Geunsik Lim via llvm-commits]

> Can you produce an IR file that, when used with upsteram llc, reproduces
the problem?
> C# IR should be no different than any other, so if you can make your
> front-end generate IR at O1 and O3

Actually, there are a lot of files from the DotNet Core run-time (e.g.
CoreCLR).
In this case, How do we reproduce related IRs with upstream 'llc' command?
On Jun 19, 2016 11:16 PM, "Renato Golin" <renato.golin at linaro.org> wrote:

> On 19 June 2016 at 06:05, Geunsik Lim <leemgs at gmail.com> wrote:
> > I have evaluated the effect of the latest clang/llvm version to resolve
> > "unassigned access (Bus error)" issue.
>
> Ok, so we still have the problem, but it's hard for me to reproduce
> because this is a C# thing.
>
> Can you produce an IR file that, when used with upsteram llc,
> reproduces the problem?
>
> C# IR should be no different than any other, so if you can make your
> front-end generate IR at O1 and O3, we could then compare and follow
> them through the back-end and see what's wrong.
>
> I'm guessing this has to do with the ARM load-store optimization pass.
>
> The best course of action now is to create a bug in Bugzilla,
> attaching the two IRs which show the bug with upstream (non-C#) LLVM,
> using "llc -triple armv7a", and copy me and compnerd at compnerd.org.
>
> Feel free to also include the original sources, your compilation
> command line and the other information in this email.
>
> cheers,
> --renato
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20160620/2830807c/attachment.html>