Jake Goulding
Jake Goulding
> or how to get more information about how exactly the SIGSEGV is happening? For this kind of problem, I've usually resorted to running `rustc` in a debugger (GDB /...
/cc #169
Licensing is my big worry about such an endeavor. I agree that we should talk to the embedded WG about this — they may have already stocked it or want...
> There are lot's of circumstances where using docker is impossible or comes at a high cost Every time I’ve ever listened to anyone talk about packaging anything for a...
Howdy 👋 Do you have any links or further information for what the expectations, requirements, privileges, etc. are as part of the team? For example, are there meetings we'd be...
Similar issue in `core::fmt::run`: ```llvm %_19 = bitcast i8* %value.1 to i1 (%"fmt::::Opaque"*, %"fmt::Formatter"*) addrspace(1)*, !dbg !26226 ```
Have we yet figured out which function pointer is being printed?
We do have a history of adding hacks like that (especially to the formatting infrastructure) to get things working again. I'd be cool with adding it, changed to hard-code the...
This occurs outside of Debug formatting. For example, the implementations of async/await executors do function pointer conversions. This could be really annoying.
Tiny Rust example: ```rust fn alpha(i: i32) -> i32 { i + 1 } static FOO: fn(i32) -> i32 = alpha; ``` The arguments to `ConstantExpr::getBitCast`: ``` (lldb) p C->dump()...