Odyssey 1.23 progress: r5 RC2

	Bottom Previous Topic Next Topic
Register To Post

« 1 ... 31 32 33 (34) 35 36 37 ... 72 »

zzd10h

Re: Odyssey 1.23 progress

Posted on: 2016/1/12 7:05 #671

Just can't stay away

@tommysammy

The same here with MEGA

samo79

Re: Odyssey 1.23 progress

Posted on: 2016/1/12 7:11 #672

Home away from home

@zzd10h & tommy

Really V3 works with MEGA ??
Then i need to try ..

EDIT: Tested but still don't work ..

Edited by samo79 on 2016/1/12 8:10:38

zzd10h

Re: Odyssey 1.23 progress

Posted on: 2016/1/12 9:05 #673

Just can't stay away

@samo79

Sort of working.
It complains many times before to begin to download and when download is complete, the file is neither in RAM: nor in T:.

kas1e

Re: Odyssey 1.23 progress

Posted on: 2016/1/12 9:10 #674

Home away from home

@all
You better try everything with latest bins (v4), as in v3 ssl support broken

Join us to improve dopus5!
AmigaOS4 on youtube

samo79

Re: Odyssey 1.23 progress

Posted on: 2016/1/12 9:48 #675

Home away from home

@zzd10h

Yeah unfortunely MEGA doesn't work well neither with Firefox (Windows)
While under Odyssey 1.23 if i try to download something i got this message:

Quote:

Out of HTML5 Offline Storage space

Your availible browser storage for MEGA cannot handle
this download size, please free up some disk space.

tommysammy

Re: Odyssey 1.23 progress

Posted on: 2016/1/12 12:04 #676

Quite a regular

@kas1e
V4 works too with ebay, paypal,MEGA,FB etc

K-L

Re: Odyssey 1.23 progress

Posted on: 2016/1/12 17:13 #677

Just can't stay away

Warning : MEGA uses a lot of memory when downloading huge files, you'd better not try this with Odyssey (even 2GB of memory won't be enough).

--
AmigaONE X1000 and Radeon RX 560

Elwood

Re: Odyssey 1.23 progress

Posted on: 2016/1/12 17:50 #678

Just can't stay away

@kas1e

I still follow :-p Maybe a developer could make some makefile magic to add the date at compilation time.

The last versions are able to run the JS Sunspider benchmark (I think the OS4depot version crashes) so here is a comparison between OWBv4 and Timberwolf:


TEST                   COMPARISON               FROM                 TO             DETAILS



===============================================================================



** TOTAL **:           ??                        ERROR                ERROR          invalid runs detected



===============================================================================



  3d:                  ??                        ERROR                ERROR          invalid runs detected

    cube:              1.81x as fast      794.2ms +/- 22.8%    438.0ms +/- 3.4%      significant

    morph:             1.76x as fast     1785.7ms +/- 20.7%   1013.1ms +/- 14.7%     significant

    raytrace:          ??                        ERROR                ERROR          invalid runs detected



  access:              ??                        ERROR                ERROR          invalid runs detected

    binary-trees:      2.07x as fast      814.9ms +/- 21.0%    392.9ms +/- 3.4%      significant

    fannkuch:          1.77x as fast      955.8ms +/- 20.8%    538.5ms +/- 0.4%      significant

    nbody:             ??                        ERROR                ERROR          invalid runs detected

    nsieve:            2.37x as fast      417.0ms +/- 26.0%    176.2ms +/- 0.6%      significant



  bitops:              -                 1618.2ms +/- 17.8%   1568.1ms +/- 22.2% 

    3bit-bits-in-byte: -                  260.5ms +/- 21.8%    210.1ms +/- 1.0%  

    bits-in-byte:      1.42x as fast      409.1ms +/- 17.9%    288.6ms +/- 0.5%      significant

    bitwise-and:       -                  400.3ms +/- 24.2%    359.0ms +/- 1.4%  

    nsieve-bits:       ??                 548.3ms +/- 22.7%    710.4ms +/- 49.0%     not conclusive: might be *1.30x as slow*



  controlflow:         5.10x as fast      569.4ms +/- 26.1%    111.6ms +/- 1.6%      significant

    recursive:         5.10x as fast      569.4ms +/- 26.1%    111.6ms +/- 1.6%      significant



  crypto:              1.32x as fast     1767.1ms +/- 23.1%   1338.2ms +/- 2.5%      significant

    aes:               -                  556.3ms +/- 26.4%    497.9ms +/- 2.9%  

    md5:               -                  566.0ms +/- 24.9%    479.0ms +/- 1.8%  

    sha1:              1.78x as fast      644.8ms +/- 23.5%    361.3ms +/- 5.5%      significant



  date:                *1.53x as slow*   1937.9ms +/- 18.9%   2974.4ms +/- 0.9%      significant

    format-tofte:      *1.56x as slow*   1019.2ms +/- 25.4%   1594.8ms +/- 0.8%      significant

    format-xparb:      *1.50x as slow*    918.7ms +/- 17.5%   1379.6ms +/- 1.4%      significant



  math:                3.19x as fast     4687.3ms +/- 22.7%   1469.9ms +/- 9.8%      significant

    cordic:            4.57x as fast     2416.6ms +/- 20.7%    528.8ms +/- 4.6%      significant

    partial-sums:      2.42x as fast     1259.1ms +/- 26.5%    520.5ms +/- 1.7%      significant

    spectral-norm:     2.41x as fast     1011.6ms +/- 25.2%    420.6ms +/- 28.5%     significant



  regexp:              *2.22x as slow*   1416.3ms +/- 24.5%   3142.6ms +/- 0.2%      significant

    dna:               *2.22x as slow*   1416.3ms +/- 24.5%   3142.6ms +/- 0.2%      significant



  string:              ??                5834.8ms +/- 22.6%   6918.4ms +/- 0.9%      not conclusive: might be *1.186x as slow*

    base64:            *1.67x as slow*    958.5ms +/- 23.9%   1597.8ms +/- 0.9%      significant

    fasta:             1.50x as fast     1637.0ms +/- 24.7%   1090.7ms +/- 1.6%      significant

    tagcloud:          *1.178x as slow*  1117.9ms +/- 18.9%   1317.1ms +/- 1.8%      significant

    unpack-code:       *1.70x as slow*   1146.4ms +/- 24.7%   1951.1ms +/- 0.7%      significant

    validate-input:    -                  975.0ms +/- 25.1%    961.7ms +/- 1.0%

So to everyone involved thanks and well done guys!!!

Severin

Re: Odyssey 1.23 progress

Posted on: 2016/1/12 18:25 #679

Just can't stay away

@zzd10h

Change the post time in dos prefs to stop those error windows closing so fast.

radzik

Re: Odyssey 1.23 progress

Posted on: 2016/1/13 5:54 #680

Just popping in

I have asked WebKit developers on the Twitter @webkit and they abandoned and will not support PPC any more.

So it looks like or we fix it in our community or in this situation I think is better to jump into new engine? Because it could possibly that after one fix WebKit , then in some time we must make other one etc.

Amiga 2000 2 MB Chip ECS, Blizzard 2060/60 MHz 128 MB Fast, Picasso II+, Deneb USB, 160 GB & DVD-RW / OS 3.9
Amiga 1200, Blizzard PPC 233/040 256 MB Fast, BVision / OS4.0, OS3.9
Pegasos II 1 GB Radeon 9250 / OS4.1
---
http://radzikowski.ovh.org

tlosm

Re: Odyssey 1.23 progress

Posted on: 2016/1/13 11:51 #681

Quite a regular

@radzik

here there is the last webkit patches from Tobias Netzel and are about R600.8.2 version for Leopard PPC .
http://sourceforge.net/projects/leopard-webkit/files/600/Sources/

In any way i say Teen4Fox is Geko and Geko working great on PowerPc ... Firefox is on ppc the version is on lnx ppc the 43.03

Edited by tlosm on 2016/1/13 12:07:54

BSzili

Re: Odyssey 1.23 progress

Posted on: 2016/1/13 13:30 #682

Quite a regular

@tlosm
You should read the 104Fox development blog more:
http://tenfourfox.blogspot.hu/2015/12 ... and-maybe-45-as-swan.html

tlosm

Re: Odyssey 1.23 progress

Posted on: 2016/1/13 17:23 #683

Quite a regular

@BSzili
all is related the macports gcc48 and gcc49 that are crappy i was reported months ago to macports mantainers ... lets hope something will be fixed

BSzili

Re: Odyssey 1.23 progress

Posted on: 2016/1/13 18:32 #684

Quite a regular

@tlosm
GCC is the least of our problems. I should have TL;DR-ed out the most important part: Mozilla has been working on its own functional programming language called Rust. Parts of Firefox are already in Rust, and the new layout engine will be written entirely in it. This means no Firefox, unless someone is willing to maintain a Rust compiler for OS4.

radzik

Re: Odyssey 1.23 progress

Posted on: 2016/1/13 19:13 #685

Just popping in

@BSzili
This means we have no other open alternatives?

I think for now is the best fix by us WebKit, but what about future? NG systems without moder web browser??

kas1e

Re: Odyssey 1.23 progress

Posted on: 2016/1/13 19:32 #686

Home away from home

@radzik
It mean that we need to find someone for current webkit, he will do the job, and then, we will use that browser for 3-5 years. And if we all will be here after 3-5 years, we can think what to do then. But for now will be enough to fix current version.

Join us to improve dopus5!
AmigaOS4 on youtube

radzik

Re: Odyssey 1.23 progress

Posted on: 2016/1/13 21:31 #687

Just popping in

I heard something that Bigfoot can do it?

tlosm

Re: Odyssey 1.23 progress

Posted on: 2016/1/13 22:12 #688

Quite a regular

@kas1e

I hope the webkit that we have will work for next 5 y.... the inet is running really fast

Kicko

Re: Odyssey 1.23 progress

Posted on: 2016/1/14 7:27 #689

Just can't stay away

You can take that 5 year with a bit of salt. You will see pages that just stop working. For example like google when they update their pages with "old browsers, please update". Like now youtube, google drive, spreedsheats etc. At least microsoft when they have "old browsers, please update" we can continue to the page anyway like for hotmail.

But a good thing is pages that migrates from flash to html5 as we lack flash.

Elwood

Re: Odyssey 1.23 progress

Posted on: 2016/1/14 9:46 #690

Just can't stay away

BSzili
Quote:

Mozilla has been working on its own functional programming language called Rust

Thanks for the highlight.
If they develop a new language, does it mean C is not as good as everyone says?

Maybe they should have tried AmigaE!

Register To Post	« 1 ... 31 32 33 (34) 35 36 37 ... 72 »
	Top Previous Topic Next Topic

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