Cliff L. Biffle

I may have been unclear -- my initial concerns are not that cortex-m is doing too much, but rather that portions of cortex-m make assumptions about environment and processor state...

Hm, I think this behavior also occurs when building different targets within a workspace... been having trouble using workspaces with xargo and wasn't sure why I was always getting rebuilds.

I am probably also changing `target-cpu`, depending on which set of projects I switch between. Can I interpret your response as suggesting that xargo maintains only a _single_ sysroot, shared...

@adamgreig - I believe this was closed inadvertently after being merely mentioned on #423. (Since I still can't work out how to turn off the trampoline without replacing the linker...

You're right, I appear to have mistaken a PR merge icon for an Issue Closed icon! My mistake. And, yeah, I assume someone out there is using it, so removing...

http://www.thingiverse.com/thingiview:24758 and http://www.thingiverse.com/thing:6620 are both fixed by the pull request I sent you: the object's name (first and last line of the STL) contains a '-' character that isn't matched...

Aaaand http://www.thingiverse.com/thing:6624 also has broken normals. Even though thingiloader recomputes the normals, the STL file is internally consistent: it's not just that 'facet normal' is wrong, but the vertex ordering/winding...

Except for bogus normals (which always show up as transparent surfaces), the issues above are fixed. :-) http://www.thingiverse.com/thing:6278 is a neat one -- apparently the ASCII parser needs to handle...

I'm kind of amazed that these objects _print_ correctly, much less render, with broken normals.

Wow, thanks for beating me to this!