Re: [eigen] Choosing the right vector implementation at run time |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/eigen Archives
]
- To: Antonio Sanchez <cantonios@xxxxxxxxxx>
- Subject: Re: [eigen] Choosing the right vector implementation at run time
- From: Ludovic Courtès <ludovic.courtes@xxxxxxxx>
- Date: Fri, 19 Nov 2021 20:56:59 +0100
- Cc: eigen@xxxxxxxxxxxxxxxxxxx
- Ironport-hdrordr: A9a23:cZy38aNYNPALHcBcTsyjsMiBIKoaSvp037BL7TEXdfUxSKalfq+V7ZcmPHPP6Ar5O0tApTnjAtjjfZq0z/ccirX5Vo3SOTUO1lHYSL2KLrGP/9QjIUDDHyJmupuIupIRNOHN
Antonio Sanchez <cantonios@xxxxxxxxxx> skribis:
> Dynamic dispatch at the lower packet level would prevent inlining and
> significantly reduce performance. You would probably need to do the
> dynamic dispatch in your own higher-level code. There is some somewhat
> related discussion here: https://gitlab.com/libeigen/eigen/-/issues/2344
Thanks for the link, very much à propos.
> Eigen is header-only, so distributions don't provide binaries of eigen
> directly.
No, but they provide binaries for code that uses Eigen.
While shared libraries can take advantage of function multi-versioning,
header-only libraries leave it up to the user to implement a solution.
Ludo’.