Le 2013-05-28 22:41, Paul Ishenin a écrit :
> 29.05.2013 10:09, Michel Catudal пишет:
>> My platform is odroid U2 with funtoo Linux, desktop is mate. Processor is a
>> 4 core arm processor from Samsung, running at 1.7Ghz with 2G of RAM, OS runs
>> on a 32G SD Card. I also have an Ubuntu system al
29.05.2013 10:09, Michel Catudal пишет:
My platform is odroid U2 with funtoo Linux, desktop is mate. Processor is a 4
core arm processor from Samsung, running at 1.7Ghz with 2G of RAM, OS runs on a
32G SD Card. I also have an Ubuntu system also on a 32G SD card, haven't tested
fpc compile on i
My platform is odroid U2 with funtoo Linux, desktop is mate. Processor is a 4
core arm processor from Samsung, running at 1.7Ghz with 2G of RAM, OS runs on a
32G SD Card. I also have an Ubuntu system also on a 32G SD card, haven't tested
fpc compile on it yet.
A few weeks ago I was able to comp
29.05.2013 1:26, Michael Ring пишет:
I did the changes, parts of the opcodes now work fine, I think I have found the
problem with the li
+ and + mfc0 op-codes, if last parameter is 0 then the asm statement is
generated wrong:
This works:
and$a0,$a0,1
this does not work:
and$
I did the changes, parts of the opcodes now work fine, I think I have
found the problem with the li + and + mfc0 op-codes, if last parameter
is 0 then the asm statement is generated wrong:
This works:
and$a0,$a0,1
this does not work:
and$a0,$a0,0
result is:
pic32mx1xxfxxxb.s:
28.05.2013 23:40, Michael Ring пишет:
Thank you Sergei, I will have a look at that code.
I have just finished inserting ugly .long 0xx statements in my code to
hardcode the missing
pieces, I am really glad you answered ;-) ;-)
I also found some statements that get translated wrong:
and
Thank you Sergei, I will have a look at that code.
I have just finished inserting ugly .long 0xx statements in my code
to hardcode the missing pieces, I am really glad you answered ;-) ;-)
I also found some statements that get translated wrong:
and $a0,$a0,0
and $a1,$a1,0
li
28.05.2013 22:50, Michael Ring пишет:
I am currently writing/porting startup code for the pic32 chips, the inline
assembler of fpc seems
to lack support for some opcodes, any idea how I can workarround this?
With grep I found for example mtc1 in opcode.inc, but mtc0 is missing, this
opcode is
I am currently writing/porting startup code for the pic32 chips, the
inline assembler of fpc seems to lack support for some opcodes, any idea
how I can workarround this?
With grep I found for example mtc1 in opcode.inc, but mtc0 is missing,
this opcode is important for the initialization of th
Thank you!
Michael
Am 28.05.13 14:56, schrieb Yury Sidorov:
Fixed in r24626. Your guesswork is right :)
Yury.
- Original Message - From: Michael Ring
To: fpc-devel@lists.freepascal.org
Sent: Tuesday, May 28, 2013 1:24 PM
Subject: Re: [fpc-devel] Problem with fpcmake when doing crossbu
Fixed in r24626. Your guesswork is right :)
Yury.
- Original Message -
From: Michael Ring
To: fpc-devel@lists.freepascal.org
Sent: Tuesday, May 28, 2013 1:24 PM
Subject: Re: [fpc-devel] Problem with fpcmake when doing crossbuild
In case my guesswork was right this would be the fix to
In case my guesswork was right this would be the fix to Makefile.fpc:
Index: Makefile.fpc
===
--- Makefile.fpc(revision 24625)
+++ Makefile.fpc(working copy)
@@ -169,8 +169,12 @@
# Always use newly created fpcmake
ifndef F
I was having troubles today installing ppcrossarm from trunk, I have a
workarround for the problem but I question myself how to really fix the
problem:
SUBARCH=armv7m
make clean buildbase CROSSINSTALL=1 OS_TARGET=embedded CPU_TARGET=arm
SUBARCH=$SUBARCH CROSSOPT="-godwarfsets -gw2 -O-"
BINUTI
13 matches
Mail list logo
