Sync with LLVM release/16.x

[kabeor]

No description provided.

[kabeor]

Build failed, waitting until next week's commit sync.

[Rot127]

Would propose to get #10 done first. After it is merged I do a rebase onto the newest release/16.x again.

[Rot127]

As @XVilka suggested we can just skip v16 and go directly to v17. @KaBeo any opjections?

[kabeor]

@Rot127 Sure, we can do that easily with CI now.

[kabeor]

Btw, CI failed since https://github.com/capstone-engine/llvm-capstone/actions/runs/5040615865, we should make sure it work before rebase to v17.

[Rot127]

@kabeor The current release/16.x branch has our auto-sync changes as well, if I see this correctly. Are you fine if we keep the release/16.x and future LLVM-release branches clean from auto-sync stuff and rebase the auto-sync onto it?

I think resolving conflicts is easier this way.
Also we do not accidentally merge LLVM stuff and overwrite auto-sync changes.

To make conflict resolving even easier, we can also think about squashing the auto-sync branch before every big rebase.

So in we end up with something like:

                 sqaush & rebase & rename
                 onto release/16.X
              +------------------------------>  auto-sync-16.X    <---- new PRs must go here.
              |                                        |
              |                                 (release/16.X)
             ...
          [commit C]
          [commit B]
          [commit A] 
          (auto-sync)

Might not be the best idea. Because it destroys the commit history for more convenience.

[kabeor]

@Rot127

Are you fine if we keep the release/16.x and future LLVM-release branches clean from auto-sync stuff and rebase the auto-sync onto it?

Yes, that would be great. I should have set the release/x.x branch to be protected.

[XVilka]

@kabeor @Rot127 LLVM just branched off to 17.x, I guess it's time to port this work on top of it. From what I saw in the git changes it shouldn't affect ARM and PPC, but will definetitely affect AArch64.

• https://github.com/llvm/llvm-project/tree/release/17.x
• https://discourse.llvm.org/t/llvm-17-0-0-rc1-released/72408
• https://discourse.llvm.org/t/llvm-17-0-0-rc2-released/72658
• https://discourse.llvm.org/t/llvm-17-0-0-rc3-released/72946
• https://discourse.llvm.org/t/llvm-17-0-0-rc4-released/73257

[kabeor]

Yep. Btw, when LLVM 17 offical version been released, the CI will auto creates a branch release/17.x.

[Rot127]

@kabeor Fancy! Will it include our changes? Or be equivalent to the LLVM release?

[kabeor]

@Rot127 It will just include llvm code. Any our changes still need to be merged into auto-sync.

[XVilka]

LLVM 17.0.1 was released finally:

• https://discourse.llvm.org/t/llvm-17-0-1-released/73549/4
• https://releases.llvm.org/17.0.1/docs/ReleaseNotes.html

[kabeor]

Let's see if CI works next Monday.

[Rot127]

closing this because we work on LLVM 18 now
#45