On Thu, Mar 17, 2016 at 1:58 PM, Martin Stransky wrote:
> Is it possible to build Rust from sources before Firefox build executes?
rustc is written in Rust, so if you only have source code and the
compilers that are currently available in Fedora, you can't build
rustc. At minimum, you need a "sta
On 03/17/2016 08:05 AM, Thinker Li wrote:
On Wednesday, March 16, 2016 at 10:22:40 PM UTC+8, Nicholas Nethercote wrote:
Even if we can fix that, it's just a lot of JS code. We can lazily import
JSMs; I wonder if we are failing to do that as much as we could, i.e. are
all these modules r
On Thu, Mar 17, 2016 at 3:30 PM, wrote:
> What about the depreciation of XP SP2?
>
Results from bug 1124017 say XP SP2 still works on binaries built with
VS2015u1. This may not always hold true. So we will need to have the XP SP2
discussion at some point. I defer to bsmedberg to start that discu
On 3/19/16 5:27 AM, cosinusoida...@gmail.com wrote:
On Thursday, 17 March 2016 12:23:32 UTC, Henri Sivonen wrote:
On Thu, Mar 17, 2016 at 1:58 PM, Martin Stransky wrote:
Is it possible to build Rust from sources before Firefox build executes?
rustc is written in Rust, so if you only have so
On Fri, Mar 18, 2016 at 4:01 AM, Sylvestre Ledru wrote:
> Le 17/03/2016 à 21:30, Henri Sivonen a écrit :
> > On Thu, Mar 17, 2016 at 2:28 PM, Sylvestre Ledru
> wrote:
> >> In Debian & Ubuntu,
> > I didn't find a rustc package on http://packages.ubuntu.com/ . What's
> > the situation on Ubuntu?
>
On 3/14/16 3:01 PM, Martin Thomson wrote:
The actual benefit is something that is only realized once a site puts
in the effort required. That is small, yes, but we're seeing sites
actively avoid password managers, hence the aggressive heuristics, and
rAC is much more likely to work for that, si
On Sat, Mar 19, 2016 at 01:45:49AM +0900, Mike Hommey wrote:
> On Fri, Mar 18, 2016 at 05:23:21PM +0200, Henri Sivonen wrote:
> > You say you don't see #5 happening. Do you see #4 happening? If not,
> > what do you see happening?
>
> At this point, I'm wondering if the best outcome wouldn't be 6)
> "Henri" == Henri Sivonen writes:
Henri> Ubuntu and Fedora don't have any version of rustc anywhere at
Henri> all.
For Fedora it's in COPR, but of course that's not official, just
something to play with.
You can follow the Fedora Rust packaging process here:
https://bugzilla.redhat.com/sh
On Friday, March 18, 2016 at 4:53:58 AM UTC-7, Sylvestre Ledru wrote:
> Le 17/03/2016 à 21:30, Henri Sivonen a écrit :
> > On Thu, Mar 17, 2016 at 2:28 PM, Sylvestre Ledru wrote:
> >> In Debian & Ubuntu,
> > I didn't find a rustc package on http://packages.ubuntu.com/ . What's
> > the situation on
Do we have a plan being executed to make sure that when Gecko
components written in Rust ship on the release channel in
Mozilla-produced builds the also ship in the Firefox packages of
various Linux distributions?
If not, we really need to put such a plan in place, since it would be
bad to have a
On Friday, March 18, 2016 at 2:07:34 PM UTC+11, jww...@mozilla.com wrote:
> https://hg.mozilla.org/mozilla-central/file/3e04659fdf6aef792f7cf9840189c6c38d08d1e8/mfbt/UniquePtr.h#l182
>
> "To unconditionally transfer ownership of a UniquePtr into a method, use a
> |UniquePtr| argument. To conditi
On Thu, Mar 17, 2016 at 2:28 PM, Sylvestre Ledru wrote:
> In Debian & Ubuntu,
I didn't find a rustc package on http://packages.ubuntu.com/ . What's
the situation on Ubuntu?
> we use the official binaries provided to be able to build rust.
My same logic, can Mozilla-built rustc be used to build
https://hg.mozilla.org/mozilla-central/file/3e04659fdf6aef792f7cf9840189c6c38d08d1e8/mfbt/UniquePtr.h#l182
"To unconditionally transfer ownership of a UniquePtr into a method, use a
|UniquePtr| argument. To conditionally transfer ownership of a resource into a
method, should the method want it,
Le 17/03/2016 à 14:01, Martin Stransky a écrit :
> On 03/17/2016 01:47 PM, Sylvestre Ledru wrote:
>
> [...]
>
>> One way which would make the life of Linux distro way easier would be
>> to maintain the Firefox rust code in a way it could compile using older rust
>> compiler.
>>
>> For example, ima
On Thu, Mar 10, 2016 at 8:14 AM, Gregory Szorc wrote:
> Visual Studio 2015 has been out for a while. Many people have put in work
> to make Firefox build on it. The time has come to officially transition
> release builds from Visual Studio 2013 to Visual Studio 2015.
>
> This email serves as an i
Le 17/03/2016 à 11:59, Henri Sivonen a écrit :
> Do we have a plan being executed to make sure that when Gecko
> components written in Rust ship on the release channel in
> Mozilla-produced builds the also ship in the Firefox packages of
> various Linux distributions?
[...]
>
> Can we get Debian st
On Thu, Mar 17, 2016 at 04:59:29PM -0700, bander...@mozilla.com wrote:
> Hi,
>
> This is a matter that concerns the Rust team a lot. From the Rust side
> we want to make it possible for Debian and Fedora (as a proxy for all
> distros) to be able to bootstrap off of their own rustc's and keep up
>
What about the depreciation of XP SP2?
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
On 3/16/16 2:39 PM, Domenic Denicola wrote:
Now at https://html.spec.whatwg.org/#navigator.hardwareconcurrency (plus
https://html.spec.whatwg.org/#navigator and
https://html.spec.whatwg.org/#workernavigator).
Thank you.
To close the loop on this, given lack of objections I am going to go
ah
On Wednesday, March 16, 2016 at 10:22:40 PM UTC+8, Nicholas Nethercote wrote:
> Even if we can fix that, it's just a lot of JS code. We can lazily import
> JSMs; I wonder if we are failing to do that as much as we could, i.e. are
> all these modules really needed at start-up? It would be grea
Hi!
I tested over the last months Firefox Sync... and because of some problems I
did in the last days a lot more test with it and noted a lot of problems with
it to report...
Because it is really a lot, I will split it in multiple mails within this
topic...
Feedback to the problems would be n
Conceptually already_AddRefed is a move reference. And it's destructor
asserts (in debug builds) that the reference was indeed moved, so it cannot
be used as a conditional transfer under any circumstances.
- Kyle
On Thu, Mar 17, 2016 at 8:07 PM, wrote:
>
> https://hg.mozilla.org/mozilla-centra
On 03/17/2016 01:47 PM, Sylvestre Ledru wrote:
[...]
One way which would make the life of Linux distro way easier would be
to maintain the Firefox rust code in a way it could compile using older rust
compiler.
For example, imagine that the next Debian stable or Ubuntu LTS ships using Rust
2.
On 15/03/2016 04:34, Nicholas Nethercote wrote:
> - "heap-overhead" is 4 MiB per process. I've looked at this closely.
> The numbers tend to be noisy.
>
> - "page-cache" is pages that jemalloc holds onto for fast recycling. It is
> capped at 4 MiB per process and we can reduce that with a
Le 17/03/2016 à 21:30, Henri Sivonen a écrit :
> On Thu, Mar 17, 2016 at 2:28 PM, Sylvestre Ledru wrote:
>> In Debian & Ubuntu,
> I didn't find a rustc package on http://packages.ubuntu.com/ . What's
> the situation on Ubuntu?
I thought it was already synced for xenial. I just filled the request:
On 17/03/2016 11:59, Henri Sivonen wrote:
> (I'm assuming that it won't be a big deal to get
> Gentoo to pick up the most recent rustc when the use case shows up.)
Gentoo has an official portage overlay for rust with the latest stuff
available:
https://github.com/gentoo/gentoo-rust
It should be
Le 17/03/2016 à 13:22, Henri Sivonen a écrit :
> On Thu, Mar 17, 2016 at 1:58 PM, Martin Stransky wrote:
>> Is it possible to build Rust from sources before Firefox build executes?
> rustc is written in Rust, so if you only have source code and the
> compilers that are currently available in Fedor
On Thursday, 17 March 2016 12:23:32 UTC, Henri Sivonen wrote:
> On Thu, Mar 17, 2016 at 1:58 PM, Martin Stransky wrote:
> > Is it possible to build Rust from sources before Firefox build executes?
>
> rustc is written in Rust, so if you only have source code and the
> compilers that are currentl
On Fri, Mar 18, 2016 at 12:05 PM, wrote:
> For Firefox this would require a lot of discipline. For Rust it would be a
> massive challenge coming up with a maintainable scheme.
Frankly, I think the probability that either the Gecko or Rust teams would
commit significant portions of their limited
On Fri, Mar 18, 2016 at 1:10 AM, Nicolas B. Pierron
wrote:
> This is not better from the point of view of distributions policy.
>
> This is better because you remove a lot of unknown variables from the
> equation, and rely on a real package manager to package and distribute
> software with its dep
On 03/17/2016 10:59 AM, Henri Sivonen wrote:
My concern is that Linux distributions tend to have a policy that
binary packages have to be buildable from source packages using the
tools that are available in the package repository of the distro.
Considering the current state of rustc availability
> On Thu, Mar 17, 2016 at 3:30 PM,
> mailto:yuhongbao_...@hotmail.com>> wrote:
> What about the depreciation of XP SP2?
>
> Results from bug 1124017 say XP SP2 still works on binaries built with
> VS2015u1. This may not always hold true. So we will need to have the XP
> SP2 discussion at some
I seem to remember that our ChromeWorkers (SessionWorker,
PageThumbsWorker, OS.File Worker) were pretty memory-hungry, but I don't
see any workers there. Does this mean that they have negligible overhead
or that they are only in the parent process?
Cheers,
David
On 15/03/16 04:34, Nicholas Nethe
> I've been assuming that Firefox would use the Rust "stable" channel
> compiler on the Firefox "release" channel, but I don't know if that
> has ever been really *decided* anywhere. Has it been decided?
Your assumption is correct. For gecko integration related work we use
the stable version of th
On Thu, Mar 17, 2016 at 9:50 AM, Nicolas B. Pierron <
nicolas.b.pier...@mozilla.com> wrote:
> Source compressions should already be enabled. I think we do not do it
> for small sources, and for Huge sources, as the compression would either be
> useless, or it would take a noticeable amount of tim
The firefox-sdk/sdk/lib is duplicate of firefox-sdk/lib
That's was not necessary.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Just piling on here - I think that the conditional-move idiom is super
confusing and we should forbid it. If some specific class needs such an
idiom, they can build a special container that can be passed by
lvalue-reference.
On Thu, Mar 17, 2016 at 11:14 PM, Xidorn Quan wrote:
> On Fri, Mar 18,
Hi,
This is a matter that concerns the Rust team a lot. From the Rust side
we want to make it possible for Debian and Fedora (as a proxy for all
distros) to be able to bootstrap off of their own rustc's and keep up
with the Rust release process.
We have a [good idea][1] about how to accomplish th
On 03/17/2016 08:30 PM, Henri Sivonen wrote:
On Thu, Mar 17, 2016 at 4:11 PM, Nicolas B. Pierron
wrote:
I guess one of the thing we could do is use an alternative solution, such as
an external package manager which can work side-by-side with the host, such
as zero-install, Portage, or Nix.
I
On Fri, Mar 18, 2016 at 2:29 AM, David Rajchenbach-Teller <
dtel...@mozilla.com> wrote:
>
> I seem to remember that our ChromeWorkers (SessionWorker,
> PageThumbsWorker, OS.File Worker) were pretty memory-hungry, but I don't
> see any workers there. Does this mean that they have negligible overhead
On 03/17/2016 11:59 AM, Henri Sivonen wrote:
Do we have a plan being executed to make sure that when Gecko
components written in Rust ship on the release channel in
Mozilla-produced builds the also ship in the Firefox packages of
various Linux distributions?
If not, we really need to put such a
On 3/17/16 9:50 AM, Nicolas B. Pierron wrote:
Note, this worked on B2G, but this would not work for Gecko. For example
all tabs addons have to use toSource to patch the JS functions.
Note that we do have the capability to lazily load the source from disk
when someone does this, and we do use i
On Tuesday, March 15, 2016 at 2:08:50 AM UTC-4, Boris Zbarsky wrote:
> On 3/15/16 12:59 AM, Domenic Denicola wrote:
> > Filed https://github.com/whatwg/html/issues/879; should be able to have it
> > in the spec by sometime tomorrow.
>
> Thank you. That's a lot more useful than me snarking, for s
43 matches
Mail list logo