Odyssey 1.23 progress: r5 RC2

	Bottom Previous Topic Next Topic
Register To Post

(1) 2 3 4 ... 72 »

pseudaxos

Re: Odyssey 1.23 progress

Posted on: 2014/1/22 18:12 #11

Just popping in

@Kas1e

Thanks !

Sam460ex
Os4.1 Final Edition
2GB Fast Memory
envy 24 HT sound card
HD R9 TRIX 280X 3GO GDDR5

ddni

Re: Odyssey 1.23 progress

Posted on: 2014/1/22 18:38 #12

Just can't stay away

@kas1e

"Need speelchecking.library" is this an intentional spelling pun? ;)

djrikki

Re: Odyssey 1.23 progress

Posted on: 2014/1/22 19:38 #13

Quite a regular

@ddni

+1

Seriously though it is great to read regular updates.

yssing

Re: Odyssey 1.23 progress

Posted on: 2014/1/22 20:00 #14

Just popping in

Very cool :)

Alien Air Attack

SAM440@733 mhz as main amiga.

Kicko

Re: Odyssey 1.23 progress

Posted on: 2014/1/22 20:34 #15

Just can't stay away

Nice to see its already on work :D

magnetic

Re: Odyssey 1.23 progress

Posted on: 2014/1/22 21:43 #16

Just popping in

kas1e for PRESIDENT!

Younghippie

Re: Odyssey 1.23 progress

Posted on: 2014/1/22 22:23 #17

Just popping in

@kas1e

Thanks! Nice to see it´s going forward.

spotUP

Re: Odyssey 1.23 progress

Posted on: 2014/1/22 23:39 #18

Just can't stay away

NICE!

Marko

Re: Odyssey 1.23 progress

Posted on: 2014/1/23 0:20 #19

Quite a regular

Cool!

AmigaOS 4.1 FE Update 2 on Sam440ep-flex, 800Mhz, 1GB RAM, Radeon 9250 Resized Image

A1200/040, 2+4MB, external 3.5''HDD / A1200 (spare) / A500+ (sold) / C128 (sold)
http://m4rko.com/AMIGA

kas1e

Re: Odyssey 1.23 progress

Posted on: 2014/1/24 11:20 #20

Home away from home

@all
Ok, so far all the linking errors fixed, everything ok, but, for making final binary there is one linking and fresh error remain (like anyone think it will be the same as with other versions:) ).

So, problem (i think) is the size of the final binary, when we use ffmpeg together with latest webkit core. ffmpeg static libraries by itself is about 100mb of size now (latest ones, even just libavcodec.a bigger on 20mb now), as well as all main odysseys static libs are about 80mb of size.

In end, when final linking is about to be done , it fails with such errors:

Quote:

main.cpp:(.text+0x130): relocation truncated to fit: R_PPC_REL24 against symbol `setjmp' defined in .text section in /usr/local/amiga/ppc-amigaos/SDK/newlib/lib/libc.a(stub_setjmp.o)
../Tools/OWBLauncher/CMakeFiles/owb.dir/MorphOS/main.cpp.obj: In function `create_application(char*)':
main.cpp:(.text+0x374): relocation truncated to fit: R_PPC_REL24 against symbol `__getreent' defined in .text section in /usr/local/amiga/ppc-amigaos/SDK/newlib/lib/libc.a(stub___getreent.o)
main.cpp:(.text+0x38c): relocation truncated to fit: R_PPC_REL24 against symbol `fwrite' defined in .text section in /usr/local/amiga/ppc-amigaos/SDK/newlib/lib/libc.a(stub_fwrite.o)
../Tools/OWBLauncher/CMakeFiles/owb.dir/MorphOS/main.cpp.obj: In function `open_libs()':
main.cpp:(.text+0xa5c): relocation truncated to fit: R_PPC_REL24 against symbol `__getreent' defined in .text section in /usr/local/amiga/ppc-amigaos/SDK/newlib/lib/libc.a(stub___getreent.o)
main.cpp:(.text+0xa74): relocation truncated to fit: R_PPC_REL24 against symbol `fwrite' defined in .text section in /usr/local/amiga/ppc-amigaos/SDK/newlib/lib/libc.a(stub_fwrite.o)
main.cpp:(.text+0xaa0): relocation truncated to fit: R_PPC_REL24 against symbol `__getreent' defined in .text section in /usr/local/amiga/ppc-amigaos/SDK/newlib/lib/libc.a(stub___getreent.o)
main.cpp:(.text+0xab8): relocation truncated to fit: R_PPC_REL24 against symbol `fwrite' defined in .text section in /usr/local/amiga/ppc-amigaos/SDK/newlib/lib/libc.a(stub_fwrite.o)
main.cpp:(.text+0xac4): relocation truncated to fit: R_PPC_REL24 against symbol `__getreent' defined in .text section in /usr/local/amiga/ppc-amigaos/SDK/newlib/lib/libc.a(stub___getreent.o)
main.cpp:(.text+0xadc): relocation truncated to fit: R_PPC_REL24 against symbol `fwrite' defined in .text section in /usr/local/amiga/ppc-amigaos/SDK/newlib/lib/libc.a(stub_fwrite.o)
main.cpp:(.text+0xc14): relocation truncated to fit: R_PPC_REL24 against symbol `__getreent' defined in .text section in /usr/local/amiga/ppc-amigaos/SDK/newlib/lib/libc.a(stub___getreent.o)
main.cpp:(.text+0xc2c): additional relocation overflows

And there is more , for almost all usual amiga functions from lib.a, and in all the objects.

All what i can notice while linking happens, is that it all reach moment when binary are 145mb of size (holy shit!), and then on moment when it all should be done, it fail with such errors.

I of course can think that stripping and co will help after all, and binary can be reduced to something more adequate, but, as far as i understand, all those errors happens now because of the size of binary.

All what i found currently is that thread: http://www.amigans.net/modules/xforum ... t_id=47726#forumpost47726
which in end mean "recompiling everything with -mlongcall", but problem that the code gets slightly slower then and so you know what results is.. I already do test if -mlongcall will help on one of objects, and it is, i can recompile everything with it, but it also mean code will be slower.

Any ideas / suggestions ?

Edited by kas1e on 2014/1/24 11:40:42
Edited by kas1e on 2014/1/24 11:43:20
Edited by kas1e on 2014/1/24 11:50:01
Edited by kas1e on 2014/1/24 11:50:32

Join us to improve dopus5!
AmigaOS4 on youtube

ddni

Re: Odyssey 1.23 progress

Posted on: 2014/1/24 11:54 #21

Just can't stay away

Total lamer suggestion, but can split the binary into a core and add on type set up?

AmigaOne X1000.
Radeon RX550

http://www.tinylife.org.uk/

afxgroup

Re: Odyssey 1.23 progress

Posted on: 2014/1/24 12:05 #22

Amigans Defender

try to enlarge the text section using something like -Ttext=2000000 to cflags/cppflags

i'm really tired...

kas1e

Re: Odyssey 1.23 progress

Posted on: 2014/1/24 12:06 #23

Home away from home

@afxgroup
Quote:

try to enlarge the text section using something like -Ttext=2000000 to cflags/cppflags

For all the objects ? (that also mean recompiling of beast => one more day).

Join us to improve dopus5!
AmigaOS4 on youtube

kas1e

Re: Odyssey 1.23 progress

Posted on: 2014/1/24 12:12 #24

Home away from home

@afxgroup
Tried on one of objects (where -mlongcall make it works), and -Ttext=2000000 didn't help

Join us to improve dopus5!
AmigaOS4 on youtube

kas1e

Re: Odyssey 1.23 progress

Posted on: 2014/1/24 12:26 #25

Home away from home

@all
Found that in morphos build -mlongcall also in use. So, will rebuild everything with it now (damn!). Through, that mean 1.23 will be slower somewhere. Dunno when -mlongcall start to be in use , but till 1.17 there wasn't. But as Fab add it then its all expected, so one more day till binary done as whole recompile starts. But for sure with -mlongcall things going to be slower (google says same). As well as attaching that huge-fat ffmpeg libraries will make loading of binary slower, too, as binary will be bigger.

Join us to improve dopus5!
AmigaOS4 on youtube

afxgroup

Re: Odyssey 1.23 progress

Posted on: 2014/1/24 12:33 #26

Amigans Defender

which cpu are you using? did you use the -j switch when compiling?

i'm really tired...

kas1e

Re: Odyssey 1.23 progress

Posted on: 2014/1/24 12:36 #27

Home away from home

@afxgroup
Quote:

which cpu are you using? did you use the -j switch when compiling?

Of course all with -jX, it speed up things a little , but as i build it on cygwin on notebook which i just buy for some simple text work that just tells and speed pretty sucky. I thinking about build it on some of my remote linux servs, but repeat all the same steps now which i do in last days but on another serv pretty boring, so better just wait a day :)

Join us to improve dopus5!
AmigaOS4 on youtube

afxgroup

Re: Odyssey 1.23 progress

Posted on: 2014/1/24 12:41 #28

Amigans Defender

cygwin has become too slow.. try with linux/mac and you will notice the differences..

i'm really tired...

kas1e

Re: Odyssey 1.23 progress

Posted on: 2014/1/24 12:52 #29

Home away from home

@afxgroup
Yep, i already tested it with dopus5 : whole dopus5 builds on my cygwin for about 30 minutes i think. On dopus5.org serv (which is just some common linux with more or less ok cpu) , build whole dopus5 for about 7 minutes. That for os4 version, os3 version builds even faster. Its and cygwin slower in few times, and cpu differences make sense of course :)

Join us to improve dopus5!
AmigaOS4 on youtube

Fab

Re: Odyssey 1.23 progress

Posted on: 2014/1/24 13:37 #30

Just popping in

@kas1e

Well, I didn't use the longcall option without reason. The executable got too large at some point, and it couldn't be avoided without annoying hacks.

That being said, you're not forced to make it even 50 MB larger than required by linking the whole ffmpeg libraries. Just build the decoders/formats/parsers in the HTML5 specification, it will take less than 5MB then.

For instance, using the following options would be a good start:
--arch=powerpc --cpu=powerpc --enable-runtime-cpudetect --disable-indevs --disable-protocols --enable-protocol=file --disable-network --disable-encoders --disable-decoders --disable-hwaccels --disable-muxers --disable-demuxers --disable-parsers --disable-bsfs --disable-devices --disable-filters --enable-decoder=aac --enable-decoder=aac_latm --enable-decoder=h264 --enable-decoder=mp3 --enable-decoder=theora --enable-decoder=vorbis --enable-demuxer=aac --enable-demuxer=aac_latm --enable-parser=aac --enable-parser=aac_latm --enable-demuxer=mp3 --enable-demuxer=mov --enable-demuxer=ogg --enable-parser=mpegaudio --enable-bsf=h264_mp4toannexb --enable-decoder=pcm --enable-decoder=wav --enable-demuxer=flv --enable-decoder=flv --enable-decoder=h263 --enable-decoder=vp8 --enable-demuxer=vp8 --enable-parser=vp8 --enable-decoder=vp9 --enable-demuxer=vp9 --enable-parser=vp9 --enable-bsf=aac_adtstoasc --enable-decoder=mpeg4 --enable-parser=mpeg4video --enable-demuxer=matroska)

Oh, and by the way, you probably won't even notice a difference between using longcall or not in an application like Odyssey. I didn't see any in benchmarks, at least.

Register To Post	(1) 2 3 4 ... 72 »
	Top Previous Topic Next Topic

Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )