-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I've enabled |make tidy| on Travis, and expanded it to check for
whitespace errors as well as missing license blocks (which it did
before). [1] For reference, no longer allowed are:
* tabs,
* carriage returns,
* trailing whitespace,
* missing
> I've enabled |make tidy| on Travis, and expanded it to check for
> whitespace errors as well as missing license blocks (which it did
> before). [1] For reference, no longer allowed are:
Did this get disabled at some pint? `make tidy` used to run as part of
`make check`. Or perhaps I'm confusing
On 07/11/2014 12:21 PM, Jack Moffitt wrote:
I've enabled |make tidy| on Travis, and expanded it to check for
whitespace errors as well as missing license blocks (which it did
before). [1] For reference, no longer allowed are:
Did this get disabled at some pint? `make tidy` used to run as part o
On 07/10/2014 11:11 PM, Nicholas Nethercote wrote:
On Thu, Jul 10, 2014 at 10:34 PM, Patrick Walton wrote:
Historically, Rust's large stacks were due to the fact that at the time
stack growth was removed, rustc had worse codegen than it did today,
resulting in frames with very large activation
- Original Message -
> Rust does have 2MB stacks by default. These giant numbers are surprising.
In Gecko, we've found that almost anytime we start measuring something, we find
something surprising. ;)
Andrew
___
dev-servo mailing list
dev-se
On Jul 11, 2014, at 12:04 PM, Brian Anderson wrote:
> Rust does have 2MB stacks by default. These giant numbers are surprising.
These giant numbers aren’t too surprising, since LLVM isn’t that great at
optimizing stack space. Is Rust inserting the lifetime.start and lifetime.end
markers?
http
On 7/11/14 12:54 PM, Cameron Zwarich wrote:
These giant numbers aren’t too surprising, since LLVM isn’t that
great at optimizing stack space. Is Rust inserting the lifetime.start
and lifetime.end markers?
http://llvm.org/docs/LangRef.html#llvm-lifetime-start-intrinsic
Use of lifetime markers is
7 matches
Mail list logo
