Most (all?) passes have a maximum LLVM version number of 16.

[nielsdos]

Describe the Bug

Most passes have a maximum LLVM version number of 16.
For example, the type based alias analysis pass has:

inkwell/src/passes.rs

Lines 1055 to 1058 in 5c9f7fc

	#[llvm_versions(..=16)]
	pub fn add_type_based_alias_analysis_pass(&self) {
	unsafe { LLVMAddTypeBasedAliasAnalysisPass(self.pass_manager) }
	}

However, this pass is also available in LLVM 17 and 18.
Looking at the passes.rs file, it looks like most (or all?) passes define a maximum version number of 16, making them impossible to use with LLVM 17.

To Reproduce

let pm = PassManager::create(());
pm.add_type_based_alias_analysis_pass(); // Doesn't work

Expected Behavior

I expect these passes to be available for LLVM 17.

LLVM Version (please complete the following information):

• LLVM Version: 17.0.6
• Inkwell Branch Used: 0.4

Desktop (please complete the following information):

• OS: Linux

Additional Context

N/A

[TheDan64]

Not sure why this happened, thanks for reporting

[vertexclique]

Are these removed in 18? Don't we need to bump all of them compatible up to 18?

[nielsdos]

Most (all? perhaps some under a different name?) of these optimizations are still available in LLVM 18

[vertexclique]

I searched for the new pass manager doc, I couldn't find it tbh. They made it into classes where some of these are bundled into as multiple passes. https://releases.llvm.org/18.1.1/docs/NewPassManager.html#just-tell-me-how-to-run-the-default-optimization-pipeline-with-the-new-pass-manager

[vertexclique]

Btw, setting through PassManagerOptions on the master doesn't apply the underlying passes. We need to write the current pass list in 18 with new methods (whereever they are).