I just came across this, I can look into it further if you can remember how you were placing the breakpoints.

At least in some places, we're hardware if we have an index and it's been resolved.

This is what I see with a breakpoint by name at least:

(lldb) breakpoint set -n main --hardware
Breakpoint 1: where = test.o`main + 8 at test.c:11, address = 0x000000000000077c
(lldb) breakpoint list -v
Current breakpoints:
1: name = 'main'
1.1:
module = /tmp/test.o
compile unit = test.c
function = main
location = /tmp/test.c:11
address = test.o[0x000000000000077c]
resolved = false
hardware = false
hit count = 0

(lldb) run
Process 1167457 launched: '/tmp/test.o' (aarch64)
Process 1167457 stopped

• thread #​1, name = 'test.o', stop reason = breakpoint 1.1
  frame #​0: 0x0000aaaaaaaaa77c test.o`main at test.c:11
  8 Foo f attribute((aligned (64))) = { .a=1, .b=2};
  9
  10 int main() {
  -> 11 printf("---------------------------\n");
  12 printf(" f.a: %p f.b: %p\n", &f.a, &f.b);
  13 printf("---------------------------\n");
  14
  (lldb) breakpoint list -v
  Current breakpoints:
  1: name = 'main'
  1.1:
  module = /tmp/test.o
  compile unit = test.c
  function = main
  location = /tmp/test.c:11
  address = 0x0000aaaaaaaaa77c
  resolved = true
  hardware = true
  hit count = 1

(lldb)

What did you do to get the resolved but not hardware state?