So far my best guess is that the problem is the Assmebly line
mrc 15, 0, r4, cr13, cr0, {3}
in main, which means that it's trying to read from coprocessor 15,
register 13, part 3. According to
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0360e/CACEAIHG.html
that's a thread
Hi Tomi,
Anyone have any idea if that's a larger problem, or simply something
nobody has written the small handcoded ASMs needed for ARMv5 or v4?
If latter, I might be able to wrap my head around this.
The problem you've got is related to segmented stack support. It need
fix on 2 levels:
On Tue, Dec 30, 2014 at 12:09 AM, Tony Arcieri basc...@gmail.com wrote:
On Mon, Dec 29, 2014 at 1:02 PM, Kevin Cantu m...@kevincantu.org wrote:
It's easy to set up discuss to email you all the time, too: give
it a try.
I've set up Discourse this way. As a Gmail user, this is mostly fine
On Sat, Dec 27, 2014 at 7:42 PM, Bardur Arantsson wrote:
On 2014-12-27 19:13, Evan G wrote:
A little hyperbolic, considering we're all the same rust
community.
And as far as I know you can set discourse up to work like a
mailing list (i.e. email me for every post, email me even if
Hi,
I heard Packt Publishing is working on a Rust book to appear around Apr
2015.
If the author(s) are looking for technical reviewers, contact me off list as
I'd be happy to help out if needed.
as I am a beginner in Rust I would be happy to help too.
best regards
Hartmut
--
Ideas are
https://github.com/cyndis/qmlrs
qmlrs - QtQuick bindings for Rust
but , still hope qt5 binding for rust.
2014-06-12 14:25 GMT+08:00 Noam Yorav-Raphael noamr...@gmail.com:
Cool. I was afraid that it will be harder for the compiler to optimize
away the enum, but it seems to be doing fine.
(If
