Taylor Trump

Same here, latest gcc-7 on aarch64: ```cpp [ 5%] Building CXX object third-party/folly/CMakeFiles/folly.dir/src/folly/futures/Future.cpp.o In file included from /mnt/odroid/hhvm/third-party/folly/folly/futures/Future.h:506:0, from /mnt/odroid/hhvm/third-party/folly/src/folly/futures/Future.cpp:16: /mnt/odroid/hhvm/third-party/folly/folly/futures/Future-inl.h:242:6: error: prototype for ‘decltype (((folly::Future*)this)->.folly::Future::then(forward(arg), (forward)(folly::Future::then::args)...)) folly::Future::then(Executor*, Arg&&, Args&&...

The profiled binary comes from the `build` command. Normally, rust benchmarks are separate binaries running with or without the `--bench` flag. This means, at least for now, you can profile...

On Wed, 09 Nov 2016 14:25:12 -0800 ptitSeb [email protected] wrote: > I see it's cycling on a glX call... > > Try with this: a001dc33825fa2624a385670ed1c1ce2a113267e > I think it should...

On Thu, 10 Nov 2016 04:52:03 -0800 ptitSeb [email protected] wrote: > The replay in torcs works for the menu, but crashes once replay the "in-game" part for me. One has...

You could try building a pandora target rustc on some armhf machine by simply modifying the [arm target](https://github.com/rust-lang/rust/blob/master/src/librustc_back/target/arm_unknown_linux_gnueabi.rs) to suit you needs. This way you could use the method described...

Not related to this issue but there's been a major breakage (libc crate) on arm platforms (affecting x86 android too) but the good news is at least cargo can be...

BTW, could you point us to the script used to build the stage0 snapshots? Thx! EDIT: It's provided in mk/snap.mk, e.g: `make snap-stage3-H-arm-unknown-linux-gnueabihf`

**@pandora_users**, @pranith ( I saw issue https://github.com/rust-lang/rust/issues/28467) If you know how to set up and use `qemu-user` you could try the following on your pandora box to get an idea...

BTW, the OP @ReactorScram only wanted to cross-compile **for** the pandora (soft float -> arm-none-eabi) which shouldn't pose a problem if the following is true: This [reddit comment](https://www.reddit.com/r/rust/comments/3ozoyw/whats_the_arm_crosscompilation_story_right_now/cw21l4s) from 2...

Probably moot now, but with the exception of hardware division in `libstd et al.` (that's what tuning for Cortex-A7 implies) those builds already were ARMv7+NEON. (`armv7-` triple)