inlining and `--release` builds can result in weird debuginfo relative to source about rust HOT 2 OPEN

Why do you expect vld1_u8 to be present in the disassembled executable? You are building in release mode and vld1_u8 is both small and marked as #[inline], so it will be inlined. Also debuginfo is not entirely accurate in release mode, so the lack of any debuginfo corresponding to the line where you call vld1_u8 is not unexpected.

from rust.

Why do you expect vld1_u8 to be present in the disassembled executable? You are building in release mode and vld1_u8 is both small and marked as #[inline], so it will be inlined. Also debuginfo is not entirely accurate in release mode, so the lack of any debuginfo corresponding to the line where you call vld1_u8 is not unexpected.

Because in my original code from which I created the example there's a line to which to attribute the call. It currently gets annotated like this for the original code.

;     unsafe { copy_nonoverlapping(src, dst, count) }
    cdcc: fc401020     	ldur	d0, [x1, #0x1]

Lines four to five of my simple example seem to replicate the issue.

from rust.