eigen: add version cci. 20240315 (pre 3.4.1)

[mayeut]

Summary

Changes to recipe: eigen/all

Motivation

Add a cci specific version in order to be able to build #25039
The 3.4.0 version is 3 years old but unfortunately, there are no tags with all the fixes needed yet.

Details

https://gitlab.com/libeigen/eigen/-/compare/3.4.0...9df21dc8b4b576a7aa5c0094daa8d7e8b8be60f0?from_project_id=15462818&straight=false

---

• Read the contributing guidelines
• Checked that this PR is not a duplicate: list of PRs by recipe
• Tested locally with at least one configuration using a recent version of Conan

[valgur]

Use 3.4.0.cci.20240315 as the version name instead. The naming scheme for unofficial releases on CCI was recently updated by the team: #24769 (comment)

[conan-center-bot]

Conan v1 pipeline ✔️

All green in build 3 (6ee62c6cbe005134253a7953ae94cbc72c7a039f):

• eigen/3.4.0.cci.20240315:
  All packages built successfully! (All logs)

---

Conan v2 pipeline ✔️

Note: Conan v2 builds are now mandatory. Please read our discussion about it.

All green in build 3 (6ee62c6cbe005134253a7953ae94cbc72c7a039f):

• eigen/3.4.0.cci.20240315:
  All packages built successfully! (All logs)

[valgur]

LGTM, but why that specific version instead of the latest commit, though? onnxruntime currently uses a much older version altogether: https://gitlab.com/libeigen/eigen/-/commit/e7248b26a1ed53fa030c5c459f7ea095dfd276ac

[mayeut]

but why that specific version instead of the latest commit, though?

This is the latest commit on 3.4 branch: https://gitlab.com/libeigen/eigen/-/tree/3.4?ref_type=heads
onnxruntime uses a commit on that branch > 3.4.0
It's expected to become 3.4.1 in the coming months.

[AbrilRBS]

Hi @mayeut thanks a lot for the PR!

It's expected to become 3.4.1 in the coming months.

You mention that they might release the new patch version in the near future, so I wonder if it's better to wait for an official release/ask upstream to prioritize creating it. Do you have any insight into the timeline for 3.4.1?

[mayeut]

@AbrilRBS, It's been asked a couple times already:

• https://gitlab.com/libeigen/eigen/-/issues/2845
• https://gitlab.com/libeigen/eigen/-/issues/2848

The answer is when they have time in the coming months.
I'd rather not have this block an onnxruntime update.

[valgur]

I agree with @mayeut. Besides onnxruntime, I have depended on a pre-release version of Eigen in all CUDA projects that make use of it, since it gets rid of a deluge of irrelevant nvcc warnings that the stable version otherwise produces.

[AbrilRBS]

After discussing with @czoido we're moving ahead with this, thanks a lot for the extra info :)

[jcar87]

Reverted here as the team reviews how to best proceed #25150

• can't see any evidence of other package repositories publishing a pre-release of eigen outright
• using this new version in onnxruntime, is likely to cause conflicts if users also depend on anything else that depends on eigen (which would be 3.4.0). causing them to override it to the newer version, exposes them to 3 years of commits of eigen and would cause other libraries to use an untested version
• from past experience, eigen pre-releases may not be API stable, or be compatible once there is a release. especially the "unsupported" section, which onnxruntime relies on

We see risk in making an arbitrary commit available from a pre-release, and exposing it to users who either use version ranges (breaking a promise that it should resolve to release), or users who are force to override because to fix a potential conflict - eigen tends to be backwards compatible, there really isn't a guarantee that things would work, especially for any downstream dependency that uses things un unsupported.

I would try to narrow down exactly which patches of eigen are needed, and we can consider a cci version that is more minimal and minimises risks.

Additionally - it would be good to understand the urgency of having onnxruntime 1.19.0 available.