On 13 Apr 2011, at 14:22, Helmut Hartl wrote:
Am 17.03.11 12:48, schrieb Jonas Maebe:
There won't be an iOS 2.4.4 release, because it would barely work
with
current iOS SDK releases:
a) as of Xcode 3.2.0, simulator builds require the iphonesim target
that only exists in 2.5.x
b) as of Xcode
Am 17.03.11 12:48, schrieb Jonas Maebe:
There won't be an iOS 2.4.4 release, because it would barely work with
current iOS SDK releases:
a) as of Xcode 3.2.0, simulator builds require the iphonesim target
that only exists in 2.5.x
b) as of Xcode 3.2.6 and Xcode 4, all object files (including thos
OK. I understand the magnitude of the problem. I seem to have spent the best
part of a week wrapping my head around all the different ARM variants and
their different floating point capabilities. Not to mention ABIs etc etc.
Before we even get onto all the different operating systems and such.
On 17 Mar 2011, at 11:58, Thomas Schatzl wrote:
On Thu, 17 Mar 2011 11:30:42 +0100, Jonas Maebe wrote:
Tier one or not depends on someone who is willing to spend time on
maintaining, packaging and supporting it. [...]
... and has the hardware.
Anyone working on any free software project ca
Hi,
On Thu, 17 Mar 2011 11:30:42 +0100, Jonas Maebe wrote:
On 17 Mar 2011, at 10:14, michael wrote:
Is this a situation that is likely to change soon? With the
explosive growth
of the ARM processor in mobile and embedded devices it would seem
time that
it was a tier one architecture.
Tie
On 17 Mar 2011, at 10:14, michael wrote:
Is this a situation that is likely to change soon? With the
explosive growth
of the ARM processor in mobile and embedded devices it would seem
time that
it was a tier one architecture.
Tier one or not depends on someone who is willing to spend time
OK, I will have to live with my as fpu hack for the time being.
A couple of question:
1) I have built an ARM cross compiler on my PC with lazarus_first_time. How
can I get that script to build a cross compiler with the required hardware
floating point support?
2) I understand that ARM is not a
Den 16-03-2011 11:51, michael skrev:
So it seems fpc does not pass the correct options to as. Is there anyway I can
make it do so? My approach is obviously something of a hack.
Not as it is currently. I don't know why fpc doesn't pass the cpu
argument to gas. I guess it's because the arguments a
Thankyou for the tips re: floating point on the ARM. I have had some success.
Firstly uusing -CfVFPv3 in the options like so:
$ make all PP=/home/linaro/ppcarm_2.5.1 PREFIX="/opt/fpc-svn"
OPT="-dFPC_ARMEL -O- -dFPC_ABI_EABI -CfVFPv3"
did not do the trick. Neither did adding -Cparmv6 to the opti
Den 15-03-2011 11:32, michael skrev:
I am trying to understand how to work with the various floating point options
available for FPC when running on ARM under Linux. I'm not to familiar with
all this so please bear with me.
Specifically I have a system comprising an TI OMAP3530: ARM CORTEX A8 ru
On 15 Mar 2011, at 11:32, michael wrote:
$make clean all PP=/path/to/ppcarm PREFIX="/opt/fpc-svn"
OPT="-dFPC_ARMEL -O- -dFPC_ABI_EABI"
The resulting compiler works on the target but it generates software
floating
point instructions like "bl float64_mul".
Here I get stuck. I cannot get FPC
I am trying to understand how to work with the various floating point options
available for FPC when running on ARM under Linux. I'm not to familiar with
all this so please bear with me.
Specifically I have a system comprising an TI OMAP3530: ARM CORTEX A8 running
Linaro. /proc/cpuinfo reports
12 matches
Mail list logo
