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

Sat Jun 18 22:05:03 PDT 2016

>>> I think it is the best thing to do, yes.
>> Do you mean that you could successfully build and run some unit-tests
with -O3 flag + latest revision (e.g., LLVM rev 273084)?
>Yes.

I have evaluated the effect of the latest clang/llvm version to
resolve "unassigned
access (Bus error)" issue.
>From my experiment, I have still got the same error even though I used
latest commit number of clang/llvm.

invain at u1404-x64:/work/dotnet/coreclr.git$
invain at u1404-x64:/work/dotnet/coreclr.git$ clang --version
clang version 3.9.0 (https://github.com/llvm-mirror/clang.git
86fd3a3f3f5d2aa4ea5ebfe93dd742a25637121f) (
https://github.com/llvm-mirror/llvm.git
5ee364ff3a9d91ad0b2e795a8c4473f119bb4451)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /var/www/invain/llvm-latest/bin
invain at u1404-x64:/work/dotnet/coreclr.git$
invain at u1404-x64:/work/dotnet/coreclr.git$
invain at u1404-x64:/work/dotnet/coreclr.git$ llvm-link  --version
LLVM (http://llvm.org/):
  LLVM version 3.9.0svn
  Optimized build.
  Default target: x86_64-unknown-linux-gnu
  Host CPU: ivybridge
invain at u1404-x64:/work/dotnet/coreclr.git$
invain at u1404-x64:/work/dotnet/coreclr.git$

commit 5ee364ff3a9d91ad0b2e795a8c4473f119bb4451
Author: Amjad Aboud <amjad.aboud at intel.com>
Date:   Sat Jun 18 10:25:07 2016 +0000
    [codeview] Emit non-virtual method type.
    Differential Revision: http://reviews.llvm.org/D21011
    git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@273084
91177308-0d34-0410-b5e6-96231b3b80d8

Below is comparison result if the latest version of clang/llvm resolves the
issue.

* with -O1 ---> Okay.
root at u/arm1404:/unit-test/Windows_NT.x64.Release.20160519/Regressions/common/AboveStackLimit#
/unit-test/Windows_NT.x64.Release.20160511/Tests/coreoverlay-o1/corerun
 ./AboveStackLimit.exe
Beginning test case Jitting a large method at 6/18/16 5:49:02 AM
Random seed: 20010415; set environment variable CORECLR_SEED to this value
to repro

Beginning scenario: Jitting ~8099 arguments
Method JITTed and ran
Done
Ending test case at 6/18/16 5:49:03 AM

* with -O3 + latest commit number clang/llvm  ---> Failed.

root at u/arm1404:/unit-test/Windows_NT.x64.Release.20160519/Regressions/common/AboveStackLimit#
/unit-test/Windows_NT.x64.Release.20160511/Tests/coreoverlay-o3/corerun
 ./AboveStackLimit.exe
Bus error

* Kernel meessage in case of -O3

[ 2705.652284] Unhandled fault: alignment exception (0x011) at 0xb207d3ef
[ 2705.652338] pgd = eddb0000
[ 2705.652363] [b207d3ef] *pgd=86992835
[ 2705.652569] Alignment trap: not handling instruction ed940b00 at
[<b22cb226>]
[ 2705.652630] Unhandled fault: alignment exception (0x011) at 0xb207d401
[ 2705.652682] pgd = eddb0000
[ 2705.652708] [b207d401] *pgd=86992835
[ 2716.870758] Alignment trap: not handling instruction ed900b00 at
[<b21cff80>]
[ 2716.870829] Unhandled fault: alignment exception (0x011) at 0xb1f7d3ef
[ 2716.870883] pgd = eddb0000
[ 2716.870909] [b1f7d3ef] *pgd=86b40835

On Sat, Jun 18, 2016 at 11:27 PM, Renato Golin <renato.golin at linaro.org>
wrote:

>
> On 18 Jun 2016 2:46 p.m., "Geunsik Lim" <leemgs at gmail.com> wrote:
> >
> > > If this is a simple C++ file, can you try the same with 3.8.0?
> > > Or is
> > that Clang modified to work with C#?
> > Source is not simple and clang was modified.  Anyway, If I cannot
> resolve this issue
> > with clang 3.6 (old version for ARM), I am planning to build/execute
> full sources with 3.8.x (or latest commit number).
>
> I think it is the best thing to do, yes.
>
> > Do you mean that you could successfully build and run some unit-tests
> with -O3 flag + latest revision (e.g., LLVM rev 273084)?
>
> Yes.
>
> Cheers,
> Renato
>

-- 
http://leemgs.fedorapeople.org
Don't try to avoid pain if you fail.
If you decided to face the challenges in life,
you can gain a lot by giving your best.
Cheolsang Jeong's Book & life
--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20160619/6f604e2e/attachment.html>