Hi,
Just wanted to note, that there is a working MIPS buildslave again:
http://build.webkit.org/buildslaves/mips-1
It only does builds, no tests yet, we are working on that.
Thank you everyone for your help!
Unfortunately, the MIPS build is still red, because the following patch was
not yet ac
Hi,
Submitted the patch for enabling the MIPS slave in build.webkit.org.
https://bugs.webkit.org/show_bug.cgi?id=96713
Who should I send the buildbot password for the slave?
Thanks,
Gergely
On Thu, Aug 30, 2012 at 9:52 AM, Holger Freyther wrote:
> On 08/30/2012 12:10 AM, Gergely Kis wrote:
>
On 08/30/2012 12:10 AM, Gergely Kis wrote:
>
> Would this be acceptable for you?
sure, an actively and publicly maintained MIPS build would be great. We have
some documentation on how to setup a build slave in the wiki[1] and the slave
configuration files are maintained in SVN[2]. The configurat
On Wed, Aug 29, 2012 at 11:34 PM, Fu, Chao-Ying wrote:
> > On Wed, Aug 29, 2012 at 05:58:10PM +, Fu, Chao-Ying wrote:
> > > Hi All,
> > >
> > > Before a MIPS buildbot is ready, you can go ahead to
> > change the assembler or any parts of code. We (MIPS) will
> > test new code and submit p
> On Wed, Aug 29, 2012 at 05:58:10PM +, Fu, Chao-Ying wrote:
> > Hi All,
> >
> > Before a MIPS buildbot is ready, you can go ahead to
> change the assembler or any parts of code. We (MIPS) will
> test new code and submit patches that are required to fix the
> MIPS JSC build. Don't need
On Wed, Aug 29, 2012 at 05:58:10PM +, Fu, Chao-Ying wrote:
> Hi All,
>
> Before a MIPS buildbot is ready, you can go ahead to change the assembler
> or any parts of code. We (MIPS) will test new code and submit patches that
> are required to fix the MIPS JSC build. Don't need to worry ab
lto:ze...@selfish.org]
> Sent: Wednesday, August 29, 2012 12:56 PM
> To: Osztrogonac Csaba
> Cc: WebKit Development; Frederic Lepied; Fu, Chao-Ying;
> Thouraya ANDOLSI
> Subject: Re: [webkit-dev] SH4, MIPS, and legacy-ARM
> assemblers in JavaScriptCore
>
> On Wed, Aug 29, 2012 at
On Wed, Aug 29, 2012 at 12:35:04PM +0200, Osztrogonac Csaba wrote:
> Hi All,
Hi,
my two cents. I failed to engage companies building/using the respective
architectures and I think the best way forward is to remove them. I am
happy to prepare a patch for that.
holger
PS: Using the proper sender
Development
> Cc: Holger Hans Peter Freyther; Frederic Lepied; Fu,
> Chao-Ying; Thouraya ANDOLSI
> Subject: Re: [webkit-dev] SH4, MIPS, and legacy-ARM
> assemblers in JavaScriptCore
>
> Hi All,
>
> I'd like to inquire about the future of MIPS and SH4 assemblers.
>
Hi All,
We are working on updating WebKit MIPS support. In particular we have a
work in progress LLINT and DFG implementation for MIPS.
We already have results (mozilla testsuite, sunspider and v8 benchmarks run
reasonably well), but there are still some bugs that need to be fixed
before we can s
Hi All,
I'd like to inquire about the future of MIPS and SH4 assemblers.
A long time ago we had buildbots for MIPS and SH4 platforms (hosted by Holger).
But their last builds were at 29th June, machine were stopped, bots were removed
from build.webkit.org (2 months before!). Is there anyone int
The ARM support for DFG-JIT is finished, and the patch is ready to review
at bug 90198.
Regards,
Zoltan
> On the topic of JIT support, the baseline JIT's role is increasingly only
> to serve only to gather profiling data for the DFG JIT, and if you want
> high performance JavaScript on your platf
On the topic of JIT support, the baseline JIT's role is increasingly only to
serve only to gather profiling data for the DFG JIT, and if you want high
performance JavaScript on your platform you need to have the DFG JIT enabled.
As the purpose of the two JITs becomes increasingly coupled it may
Good for me. Thanks for helping us. This will help to the buildbot
maintainers as well, since if a patch cause a break where all of our names
are CC'ed, they can just disable the JIT until the fix is landed. I think
the several ports of JSC is something we should be proud of and I hope we
can keep
Ah, sorry, I misunderstood!
What about having a convention that assembly port maintainers are CC'd on bugs
that require new assembler support?
This will give you probably 10 hours heads up before the patch lands.
-F
On Jun 22, 2012, at 9:29 PM, Zoltan Herczeg wrote:
>> I don't want adding i
> I don't want adding instructions to SH4, MIPS, and legacy ARM to be a
> blocker for JSC work.
I didn't say you have to wait. I just said you should notify us that
something is coming which will break the build.
Regards,
Zoltan
___
webkit-dev mailing
> [mailto:webkit-dev-boun...@lists.webkit.org] On Behalf Of Filip Pizlo
> Sent: Friday, June 22, 2012 1:07 PM
> To: Zoltan Herczeg
> Cc: WebKit Development
> Subject: Re: [webkit-dev] SH4, MIPS, and legacy-ARM
> assemblers in JavaScriptCore
>
>
> On Jun 22, 2012, at 12:4
On Jun 22, 2012, at 12:43 PM, Zoltan Herczeg wrote:
> True, most of the changes are trivial. The problem is that the changes are
> usually appear without prior notice. A patch which depends on new macro
> assembler instructions, will obviously break the build, and we are not
> necessary there to
True, most of the changes are trivial. The problem is that the changes are
usually appear without prior notice. A patch which depends on new macro
assembler instructions, will obviously break the build, and we are not
necessary there to fix it immediately. I think most improvements require
time to
That would be the ifdef hell we currently deal with.
One option (that would keep everything building till appropriate people have
fixed whatever needs to be fixed) would simply be to disable the JIT for
effected platforms everytime something changes that is too difficult for us to
blindly fix.
Is there a way to reduce these costs other than deleting the slower-maintained
JITs? For example, could we temporarily freeze the JIT (perhaps the whole JSC
engine somehow) at old versions somehow for architectures that may take time to
catch up?
Regards,
Maciej
On Jun 22, 2012, at 10:52 AM,
The problem is that as we make changes we end up breaking the SH4, MIPS,
ARMvOld builds, which we are ostensibly not allowed to do, and so have to spend
significant amounts of time trying to ensure that the builds don't break/start
failing horribly, and then having committed the patch[es] we hav
Hi,
We (STMicroelectronics) are the maintainer of SH4 port.
We would like to continue maintaining it.
Could you please let me know what we need to do ? and feel free to assign
for me any bug related to SH4.
Regards,
Thouraya.
___
webkit-dev mailing l
Hi Filip,
we (Gabor Loki and me) are the maintainers of the traditional ARM port,
and we are willing to fix all issues. Just let us know what we need to do.
You can assign the necessary bug reports to us and we are available in the
#squirrelfish (or #webkit) channel as well.
Regards,
Zoltan
> Hi
Hi Filip,
We (MIPS Technologies) have customers that ship MIPS Qt WebKit and
Android that uses WebKit JSC. Also, we are working on the new interpreter and
the new JIT.
We think it would be ready in two months to contribute our code to webkit.org.
We have a nightly cron job that checks out s
25 matches
Mail list logo
