Re: port-arm32/50218: ARM executables linked with native linker on cortex-a9 raises SIGILL

[Zaid Ibrahime <mzaidibrahime%gmail.com@localhost>]

The following reply was made to PR port-arm32/50218; it has been noted by GNATS.

From: Zaid Ibrahime <mzaidibrahime%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: port-arm32/50218: ARM executables linked with native linker on
 cortex-a9 raises SIGILL
Date: Sat, 19 Sep 2015 11:40:02 +0530

 Also when I use -static, it crashes all the time. Could the issue be
 with linker option or static library or the size?
 As far as my observation, if i could reduce the size of the static
 library less than 6000 bytes, I could compile and execute the program
 successfully.
 
 Please help on this as I am blocked with this completely
 
 On Wed, Sep 9, 2015 at 12:30 PM, Zaid Ibrahime <mzaidibrahime%gmail.com@localhost> wrote:
 > The following reply was made to PR port-arm32/50218; it has been noted by GNATS.
 >
 > From: Zaid Ibrahime <mzaidibrahime%gmail.com@localhost>
 > To: gnats-bugs%netbsd.org@localhost
 > Cc: port-arm32-maintainer%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
 >         netbsd-bugs%netbsd.org@localhost
 > Subject: Re: port-arm32/50218: ARM executables linked with native linker on
 >  cortex-a9 raises SIGILL
 > Date: Wed, 9 Sep 2015 12:28:10 +0530
 >
 >   > what command line are you using for linking?
 >
 >  Please find the compiler/linker options that I have tried out so far.
 >  (Note: All these options resulted in SIGILL)
 >
 >  1.As in PR 49337, I have checked the following commands.(using
 >  "-static" itself results in SIGILL even for a small C program which
 >  just has return statement)
 >   > cc -Wall -O2 -static -c hello.c
 >   > cc -static -o first hello.o
 >
 >  2. # gcc -o api.o -DHAVE_CONFIG_H  -I. -I.. -I../include  -c  api.c
 >      # ld -r -o libyaml.a  api.o
 >      #gcc =E2=80=93DHAVE_CONFIG_H  =E2=80=93o  test1  -I../include test1.c a=
 >  pi.o
 >  Also I have tried to pass explicitly"-be8" to the linker which
 >  resulted in the same SIGILL
 >  (As mentioned in the previous post, I am calling one of the function
 >  in api.c from test1.c
 >  also  in the second case when I reduced library size by commenting
 >  some part of the code in api.c. I was able to execute without any
 >  issue).
 >
 >
 >  3. #gcc -DHAVE_CONFIG_H -I. -I..  -I../include    -msoft-float
 >  -mtune=3Dcortex-a9 -c -o my.o my.c
 >      #gcc -shared  -fPIC -DPIC -o ./my.o   -L/lib -L/usr/lib
 >  -msoft-float -mtune=3Dcortex-a9 -Wl,-soname libmyx.so.2
 >      #gcc -I../include -msoft-float -dynamic -mtune=3Dcortex-a9 -g -o
 >  example-deconstructor example-deconstructor.o  ./libmyx.so.2
 >
 >
 >
 >  On Wed, Sep 9, 2015 at 1:40 AM, Matt Thomas <matt%3am-software.com@localhost> wrote:
 >  > The following reply was made to PR port-arm32/50218; it has been noted by=
 >   GNATS.
 >  >
 >  > From: Matt Thomas <matt%3am-software.com@localhost>
 >  > To: gnats-bugs%NetBSD.org@localhost
 >  > Cc: port-arm32-maintainer%netbsd.org@localhost,
 >  >  gnats-admin%netbsd.org@localhost,
 >  >  netbsd-bugs%netbsd.org@localhost,
 >  >  mzaidibrahime%gmail.com@localhost
 >  > Subject: Re: port-arm32/50218: ARM executables linked with native linker =
 >  on cortex-a9 raises SIGILL
 >  > Date: Tue, 8 Sep 2015 13:07:09 -0700
 >  >
 >  >  > On Sep 8, 2015, at 5:45 AM, Zaid Ibrahime <mzaidibrahime%gmail.com@localhost> =
 >  =3D
 >  >  wrote:
 >  >  >=3D20
 >  >  > The following reply was made to PR port-arm32/50218; it has been noted=
 >   =3D
 >  >  by GNATS.
 >  >  >=3D20
 >  >  > From: Zaid Ibrahime <mzaidibrahime%gmail.com@localhost>
 >  >  > To: gnats-bugs%netbsd.org@localhost
 >  >  > Cc: port-arm32-maintainer%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,=3D20
 >  >  >      netbsd-bugs%netbsd.org@localhost
 >  >  > Subject: Re: port-arm32/50218: ARM executables linked with native =3D
 >  >  linker on
 >  >  > cortex-a9 raises SIGILL
 >  >  > Date: Tue, 8 Sep 2015 18:14:36 +0530
 >  >  >=3D20
 >  >  >> So is the function where it crashes from libgcc?
 >  >  >=3D20
 >  >  > No the first instruction of the function itself crashes(due to wrong
 >  >  > endianness). the function was compiled on the target.
 >  >
 >  >  what command line are you using for linking?=3D
 >  >
 >