On 2/4/2013 9:59 PM, Dave Mandelin wrote:
I was talking to Taras and Naveed about this today, and what also came up was:
4. Do the work to make 64-bit JS jit perf as good as 32-bit JS jit perf, and then switch
to x64 builds for Windows. There are of course many issues involved with such a switc
On Monday, February 4, 2013 1:39:46 PM UTC-8, Brian Smith wrote:
> Also, I want to echo khuey's comment: It seems like a lot of the argument
> against PGO is that, while our benchmarks are faster, users won't actually
> notice any difference. If that is true, then I agree with khuey that that is
On Friday, February 1, 2013 7:19:04 PM UTC-8, Brian Smith wrote:
> Ehsan Akhgari wrote:
>
> > Given the above, I'd like to propose the following long-term
>
> > solutions:
>
>
>
> 1. Did we try escalating a support request to Microsoft regarding this issue?
> I know it is kind of an odd thing
On 2013-02-04 4:39 PM, Brian Smith wrote:> Ehsan Akhgari wrote:
>> On 2013-02-04 11:44 AM, Ehsan Akhgari wrote:
>>> 3. What is the performance difference between Visual Studio
>>> 2012 PGO builds and Visual Studio 2010 builds? IMO, before
>>> we decide whether to disable PGO on Wind
On 2/4/2013 4:27 PM, Brian Smith wrote:
Ehsan Akhgari wrote:
Brian Smith wrote:
2. AFAICT, we did not seriously investigate the possibility of
splitting things out of libxul more. So far we've tried cutting
things off the top of the dependency tree. Maybe now we need to try
cutting things off t
Ehsan Akhgari wrote:
> On 2013-02-04 11:44 AM, Ehsan Akhgari wrote:
> > 3. What is the performance difference between Visual Studio
> > 2012 PGO builds and Visual Studio 2010 builds? IMO, before
> > we decide whether to disable PGO on Windows, we need to get
> > good benchmark resul
On 2013-02-04 4:27 PM, Brian Smith wrote:
Ehsan Akhgari wrote:
Brian Smith wrote:
2. AFAICT, we did not seriously investigate the possibility of
splitting things out of libxul more. So far we've tried cutting
things off the top of the dependency tree. Maybe now we need to try
cutting things off
Ehsan Akhgari wrote:
> Brian Smith wrote:
> > 2. AFAICT, we did not seriously investigate the possibility of
> > splitting things out of libxul more. So far we've tried cutting
> > things off the top of the dependency tree. Maybe now we need to try
> > cutting things off the bottom of the dependenc
Re-sending in case you missed this invitation over the weekend.
--Jet
- Original Message -
From: "Benoit Jacob"
To: "dev-platform" ,
"dev-plann...@lists.mozilla.org planning"
Sent: Saturday, February 2, 2013 2:05:46 PM
Subject: Rendering meeting this Monday, 2:30 PM US/Pacific
Hello,
On 02/01/2013 09:49 PM, Philip Chee wrote:
> On Thu, 31 Jan 2013 02:40:01 +0100, Robert Kaiser wrote:
>> Robert Relyea schrieb:
>>> Switching to SQLite would make this a non-issue.
>>
>> Is there a plan to do this? An open bug? Someone working on it?
>>
>> Robert Kaiser
>
> Doesn't SQLite come wit
On Mon, Feb 4, 2013 at 6:55 AM, Zack Weinberg wrote:
> On 2013-02-04 9:26 AM, Zack Weinberg wrote:
>>
>> On 2013-02-04 9:20 AM, rvj wrote:
>>>
>>> BTW Is there a pref that suppresses the annoying Preview Progress box ..
>>>
>>> or least are you able to move it out of the visible display area ?
>>
On 2013-02-04 11:44 AM, Ehsan Akhgari wrote:
3. What is the performance difference between Visual Studio 2012 PGO
builds and Visual Studio 2010 builds? IMO, before we decide whether
to disable PGO on Windows, we need to get good benchmark results for
Visual Studio **2012** PGO bui
On 2013-02-04 9:26 AM, Zack Weinberg wrote:
On 2013-02-04 9:20 AM, rvj wrote:
BTW Is there a pref that suppresses the annoying Preview Progress box ..
or least are you able to move it out of the visible display area ?
There isn't a pref,
I misremembered. Does print.show_print_progress = fa
On 2013-02-04 9:20 AM, rvj wrote:
BTW Is there a pref that suppresses the annoying Preview Progress box ..
or least are you able to move it out of the visible display area ?
There isn't a pref, but that box is going to be replaced with something
more modern and more customizable in bug 650960
BTW Is there a pref that suppresses the annoying Preview Progress box ..
or least are you able to move it out of the visible display area ?
"smaug" wrote in message
news:09edndvwwunnyjpmnz2dnuvz_rcdn...@mozilla.org...
On 02/02/2013 11:37 AM, rvj wrote:
Its been a couple of years since Ive us
many many thanks
.. rvj
"smaug" wrote in message
news:09edndvwwunnyjpmnz2dnuvz_rcdn...@mozilla.org...
On 02/02/2013 11:37 AM, rvj wrote:
Its been a couple of years since Ive used the Mozilla libraries and some
of the functionality now seems iffy
For example print preview requests now gen
I think I got a little confused.
I was thinking of "--read-var-info=yes"
instead of "--track-origins=yes".
Sorry about the confusion.
memgrind can grok --track-origins=yes with (debug build) of TB
in 64 bit linux fine.
It is "--read-var-info=yes"
that causes a big problem.
I allocated 6GB to m
On 02/02/2013 11:37 AM, rvj wrote:
Its been a couple of years since Ive used the Mozilla libraries and some of the
functionality now seems iffy
For example print preview requests now generate an invalid pointer error
error[Exception... "Component returned failure code: 0x80004003
(NS_ERROR_I
On Fri, Feb 1, 2013 at 10:19 PM, Brian Smith wrote:
> Ehsan Akhgari wrote:
> > Given the above, I'd like to propose the following long-term
> > solutions:
>
> 1. Did we try escalating a support request to Microsoft regarding this
> issue? I know it is kind of an odd thing, but it seems like if yo
(Re-posting to dev-platform -- I had replied to Nick privately by mistake.
On Fri, Feb 1, 2013 at 9:46 PM, Nicholas Nethercote
wrote:
> On Sat, Feb 2, 2013 at 9:05 AM, Ehsan Akhgari
> wrote:
> >>
> >> Has anyone tried running PGO and non-PGO builds of the same changeset
> >> to see how they feel
20 matches
Mail list logo