Now, the question is: does QNX use the same ABI as Linux on ARM? See ARM
EABI notes in includes/stg/MachRegs.h
Karel
On 01/24/13 11:59 PM, Stephen Paul Weber wrote:
Somebody claiming to be Nathan Hüsken wrote:
On 01/24/2013 07:26 PM, Stephen Paul Weber wrote:
Somebody claiming to be
On 01/24/2013 11:59 PM, Stephen Paul Weber wrote:
Somebody claiming to be Nathan Hüsken wrote:
On 01/24/2013 07:26 PM, Stephen Paul Weber wrote:
Somebody claiming to be Nathan Hüsken wrote:
Can you run it in gdb and loock what the backtrace looks like?
Did you compile with -debug?
I remember
On 24/01/13 16:58, Nathan Hüsken wrote:
On 01/24/2013 04:50 PM, Stephen Paul Weber wrote:
Somebody claiming to be Nathan Hüsken wrote:
On 01/24/2013 04:28 PM, Stephen Paul Weber wrote:
Do you think it is specifically the 3.2 that made it work?
Yes. With llvm version 3.1 I was only able to
Hey,
For me thinks have changed.
With the current ghc HEAD and llvm version 3.2 I am able to do a
registerised build for android!
I have not tested much, but Hello World works.
Regards,
Nathan
On 01/14/2013 06:15 PM, Nathan Hüsken wrote:
In a different thread (Error building ghc on raspberry
Somebody claiming to be Nathan Hüsken wrote:
Hey,
For me thinks have changed.
With the current ghc HEAD and llvm version 3.2 I am able to do a
registerised build for android!
Do you think it is specifically the 3.2 that made it work?
--
Stephen Paul Weber, @singpolyma
See
Somebody claiming to be Nathan Hüsken wrote:
On 01/24/2013 03:58 PM, Stephen Paul Weber wrote:
Somebody claiming to be Nathan Hüsken wrote:
With the current ghc HEAD and llvm version 3.2 I am able to do a
registerised build for android!
Do you think it is specifically the 3.2 that made it
On 01/24/2013 04:28 PM, Stephen Paul Weber wrote:
Somebody claiming to be Nathan Hüsken wrote:
On 01/24/2013 03:58 PM, Stephen Paul Weber wrote:
Somebody claiming to be Nathan Hüsken wrote:
With the current ghc HEAD and llvm version 3.2 I am able to do a
registerised build for android!
Do
Somebody claiming to be Nathan Hüsken wrote:
On 01/24/2013 04:28 PM, Stephen Paul Weber wrote:
Do you think it is specifically the 3.2 that made it work?
Yes. With llvm version 3.1 I was only able to get an unregisterised
build to work.
On 01/24/13 04:50 PM, Stephen Paul Weber wrote:
Somebody claiming to be Nathan Hüsken wrote:
On 01/24/2013 04:28 PM, Stephen Paul Weber wrote:
Do you think it is specifically the 3.2 that made it work?
Yes. With llvm version 3.1 I was only able to get an unregisterised
build to work.
Somebody claiming to be Stephen Paul Weber wrote:
Somebody claiming to be Nathan Hüsken wrote:
On 01/24/2013 04:28 PM, Stephen Paul Weber wrote:
Do you think it is specifically the 3.2 that made it work?
Yes. With llvm version 3.1 I was only able to get an unregisterised
build to work.
On 01/24/2013 04:50 PM, Stephen Paul Weber wrote:
Somebody claiming to be Nathan Hüsken wrote:
On 01/24/2013 04:28 PM, Stephen Paul Weber wrote:
Do you think it is specifically the 3.2 that made it work?
Yes. With llvm version 3.1 I was only able to get an unregisterised
build to work.
On 01/24/2013 05:04 PM, Karel Gardas wrote:
On 01/24/13 04:50 PM, Stephen Paul Weber wrote:
Somebody claiming to be Nathan Hüsken wrote:
On 01/24/2013 04:28 PM, Stephen Paul Weber wrote:
Do you think it is specifically the 3.2 that made it work?
Yes. With llvm version 3.1 I was only able to
On 01/24/2013 05:51 PM, Stephen Paul Weber wrote:
(...)
So... it can't find memcpy for some reason?
I'm about to try with llvm-3.2 to see if that's different.
I had similar problems with mkfifo. I believe the reason was, that in
the android nkd mkfifo is inlined.
The solution for me was
Somebody claiming to be Nathan Hüsken wrote:
On 01/24/2013 05:51 PM, Stephen Paul Weber wrote:
(...)
So... it can't find memcpy for some reason?
I'm about to try with llvm-3.2 to see if that's different.
The solution for me was to wrap mkfifo (in a function I called __mkfifo)
and used that
On 01/24/13 05:51 PM, Stephen Paul Weber wrote:
Doing a registered build with llvm-3.0 I eventually get:
inplace/bin/ghc-stage1 -o utils/hsc2hs/dist-install/build/tmp/hsc2hs
-static -H64m -O0 -fllvm -hide-all-packages -i -iutils/hsc2hs/.
-iutils/hsc2hs/dist-install/build
Somebody claiming to be Stephen Paul Weber wrote:
Somebody claiming to be Nathan Hüsken wrote:
But the symbol not found is __aeabi_memcpy, not memcpy itself ...
I can not find __aeabi_memcpy in the ghc source ...
Maybe it is not linking some required library?
I'm not sure. Most curious is
Somebody claiming to be Karel Gardas wrote:
On 01/24/13 05:51 PM, Stephen Paul Weber wrote:
Doing a registered build with llvm-3.0 I eventually get:
In function `c58Y_info':
/tmp/ghc21061_0/ghc21061_0.bc:(.text+0x42d4): undefined reference to
`__aeabi_memcpy'
collect2: ld returned 1 exit status
On 01/24/13 06:51 PM, Stephen Paul Weber wrote:
Somebody claiming to be Stephen Paul Weber wrote:
Somebody claiming to be Nathan Hüsken wrote:
But the symbol not found is __aeabi_memcpy, not memcpy itself ...
I can not find __aeabi_memcpy in the ghc source ...
Maybe it is not linking some
On 01/24/2013 07:00 PM, Stephen Paul Weber wrote:
Somebody claiming to be Karel Gardas wrote:
On 01/24/13 05:51 PM, Stephen Paul Weber wrote:
Doing a registered build with llvm-3.0 I eventually get:
In function `c58Y_info':
/tmp/ghc21061_0/ghc21061_0.bc:(.text+0x42d4): undefined reference to
Somebody claiming to be Nathan Hüsken wrote:
On 01/24/2013 07:00 PM, Stephen Paul Weber wrote:
Somebody claiming to be Karel Gardas wrote:
On 01/24/13 05:51 PM, Stephen Paul Weber wrote:
:(
Can you run it in gdb and loock what the backtrace looks like?
I can maybe get a core file and load
Somebody claiming to be Nathan Hüsken wrote:
On 01/24/2013 07:00 PM, Stephen Paul Weber wrote:
Somebody claiming to be Karel Gardas wrote:
On 01/24/13 05:51 PM, Stephen Paul Weber wrote:
So, not sure on the right solution, but when I add -lcapsthen the
linker errors go away and I can
On 01/24/2013 07:26 PM, Stephen Paul Weber wrote:
Somebody claiming to be Nathan Hüsken wrote:
On 01/24/2013 07:00 PM, Stephen Paul Weber wrote:
Somebody claiming to be Karel Gardas wrote:
On 01/24/13 05:51 PM, Stephen Paul Weber wrote:
So, not sure on the right solution, but when I add
Hi all,
Can people please file bugs about these issues when they are confirmed
to some degree? Lots of ARM LLVM stuff seems to just be floating
around mailing lists much higher chance of me or someone else
fixing if there are filed bug reports with test cases and/or patches
attached.
Austin
Somebody claiming to be Nathan Hüsken wrote:
On 01/24/2013 07:26 PM, Stephen Paul Weber wrote:
Somebody claiming to be Nathan Hüsken wrote:
Can you run it in gdb and loock what the backtrace looks like?
Did you compile with -debug?
I remember I got a stack trace with gdb like this (when doing
On 19/01/13 07:32, Stephen Paul Weber wrote:
Somebody claiming to be Stephen Paul Weber wrote:
Somebody claiming to be Nathan Hüsken wrote:
Was that an registerised or unregisterised build?
Did anyone succesfully build ghc on an arm system which produces non
crashing executables?
Just
On 01/19/13 11:37 PM, Karel Gardas wrote:
Hi,
I just build 7.6.1 release on my ubuntu 12.04.1 LTS which is hard-float
ABI distro. I used distro provided LLVM 3.0 and configured GHC with:
./configure --with-llc=/usr/bin/llc-3.0 --with-opt=/usr/bin/opt-3.0
Also the testsuite results run by:
Somebody claiming to be Karel Gardas wrote:
I just build 7.6.1 release on my ubuntu 12.04.1 LTS which is hard-float ABI
distro. I used distro provided LLVM 3.0 and configured GHC with:
Please keep in mind that GHC HEAD is completely different beast as
there is new codegen put on by defaul
On 01/20/13 07:39 PM, Stephen Paul Weber wrote:
Somebody claiming to be Karel Gardas wrote:
I just build 7.6.1 release on my ubuntu 12.04.1 LTS which is
hard-float ABI distro. I used distro provided LLVM 3.0 and configured
GHC with:
Please keep in mind that GHC HEAD is completely different
I got this error too.
In my case it helped to install llvm-3.0 next to llvm (in ubuntu the
executables are than called llc-3.0 and opt-3.0).
I believe this error just came in the first phase, and was caused by the
preinstalled ghc-7.4.2.
But I am not sure.
On 01/19/2013 07:45 AM, Stephen Paul
Somebody claiming to be Ben Gamari wrote:
Stephen Paul Weber singpol...@singpolyma.net writes:
Trying that gives me:
Warning: Couldn't figure out LLVM version!
Make sure you have installed LLVM
ghc: could not execute: opt-3.0
I'm using LLVM 3.1.
Are you certain the opt-3.0 is in
Hi,
I just build 7.6.1 release on my ubuntu 12.04.1 LTS which is hard-float
ABI distro. I used distro provided LLVM 3.0 and configured GHC with:
./configure --with-llc=/usr/bin/llc-3.0 --with-opt=/usr/bin/opt-3.0
And resulting ghc-stage2 is not only able to complete the build but also
Somebody claiming to be Nathan Hüsken wrote:
Was that an registerised or unregisterised build?
Did anyone succesfully build ghc on an arm system which produces non
crashing executables?
Just finally got a BB10 device set up so I can test my cross-compiler on the
ARM and I get:
Process
Somebody claiming to be Stephen Paul Weber wrote:
Somebody claiming to be Nathan Hüsken wrote:
Was that an registerised or unregisterised build?
Did anyone succesfully build ghc on an arm system which produces non
crashing executables?
Just finally got a BB10 device set up so I can test my
Somebody claiming to be Stephen Paul Weber wrote:
Somebody claiming to be Stephen Paul Weber wrote:
Somebody claiming to be Nathan Hüsken wrote:
Was that an registerised or unregisterised build?
Did anyone succesfully build ghc on an arm system which produces non
crashing executables?
Just
In a different thread (Error building ghc on raspberry pi):
On 01/08/2013 12:27 PM, Thijs Alkemade wrote:(...)
I did eventually finish building stage2, but the final executable
segfaulted on start.
I haven't investigated much why that happened, the days it takes to
rebuild it just
made me
hi nathan,
On Jan 14, 2013, at 6:15 PM, Nathan Hüsken nathan.hues...@posteo.de wrote:
Did anyone succesfully build ghc on an arm system which produces non
crashing executables?
I am asking, because I build a arm-linux-androideabi cross compiler, but
the executables crash.
Only in an
On 01/14/13 06:15 PM, Nathan Hüsken wrote:
In a different thread (Error building ghc on raspberry pi):
On 01/08/2013 12:27 PM, Thijs Alkemade wrote:(...)
I did eventually finish building stage2, but the final executable
segfaulted on start.
I haven't investigated much why that happened, the
(CC'ing glasgow-haskell-users, as it got lost somehow. A message or
two from me and Karel are also missing the list.)
On Mon, Jan 14, 2013 at 1:27 PM, Ben Gamari bgamari.f...@gmail.com wrote:
Austin Seipp mad@gmail.com writes:
I've been working on ARM the past weekend. Here's where I'm at
On 01/14/13 08:49 PM, Austin Seipp wrote:
Very true. It would be very nice if we could handle this issue
automatically after we figure out the proper way to handle it manually.
I think Karel is right that we may be able to get 90% of the way there
with a short hack in DriverPipeline, with some
39 matches
Mail list logo
