Correct the definition of pthread_t on Darwin

[chengr4]

Description

This PR fixes #2903. This PR picks up the work started by @highjeans in #4336 (close #4336) which had stalled. I just followed up the comments from @tgross35 in the PR and tried to finish it.

Thanks for leaving a great start point to study this crate.

Sources

• https://github.com/apple-oss-distributions/xnu/blob/8d741a5de7ff4191bf97d57b9f54c2f6d4a15585/EXTERNAL_HEADERS/sys/_pthread/_pthread_types.h#L103
• https://github.com/apple-oss-distributions/libpthread/blob/main/include/sys/_pthread/_pthread_t.h#L31

Checklist

• Relevant tests in libc-test/semver have been updated
• No placeholder or unstable values like *LAST or *MAX are
  included (see #3131)
• Tested locally (cd libc-test && cargo test --target mytarget);
  especially relevant for platforms that may not be checked in CI

[chengr4]

Hi @tgross35,

Could you help me understand why pub use new::*; and pub use crate::unix::*; in src/lib.rs conflict with each other, while other modules do not?

[highjeans]

Hi @chengr4, thanks for finishing this! I really wanted to do this myself but I got caught up in a bunch of work for my university so I ended up forgetting about this.

One thing to note, since now opaque_pthread_t is now just an empty enum, we dont need any of the new constants defined in apple/b32/mod.rs and apple/b64/mod.rs.

Also make sure to run the style checker in /ci/style.py before this is ready!

[chengr4]

@highjeans Thank for answering; I totally forgot 🫠. Again, Thanks for leaving the PR for me to study this crate.

@tgross35

Actually, I failed cargo test --test ctest at my local.

bad `ELAST` value at byte 0: rust: 106 (0x6a) != c 107 (0x6b)
    rust bytes: 6a 00 00 00
    c bytes:    6b 00 00 00
bad `HOST_VM_INFO64_COUNT` value at byte 0: rust: 38 (0x26) != c 40 (0x28)
    rust bytes: 26 00 00 00
    c bytes:    28 00 00 00
bad `vm_statistics64_data_t` size: rust: 152 != c 160
bad `vm_statistics64` size: rust: 152 != c 160
size of `vm_statistics64_data_t` is 160 in C and 152 in Rust

size of `struct vm_statistics64` is 160 in C and 152 in Rust

Can you please guide me how to evaluate and fix this bug?

[JohnTitor]

@chengr4 because your system has different version(s) than CI, I think. It's fine as long as CI passes (unless it's unspported).
Could you squash commits into one? Otherwise LGTM on my end.

[chengr4]

ok will do it after 6/12

[rustbot]

⚠️ Warning ⚠️

• The following commits have merge commits (commits with multiple parents) in your changes. We have a no merge policy so these commits will need to be removed for this pull request to be merged.

  • 48b9de4
  • 8924db4

  You can start a rebase with the following commands:

  $ # rebase
  $ git pull --rebase https://github.com/rust-lang/libc.git main
  $ git push --force-with-lease
  

[rustbot]

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

[chengr4]

@JohnTitor if commit mesage is not clear enough, help me fix it. Thanks