Please make any modifications you like to the individual package pages. Especially desirable contributions are:
Elaborating on details of what the package is, where they are sparse.
Mentioning yourself if you are actively working on it or have some expertise that you'd like to share.
Adding labels to the relevant pages if you (for example) know that something includes NEON optimisations or is known to compile on Arm (with either GCC or the Arm Compiler suite).
Sharing instructions, gotchas, recipes, results and anything else that you think could help those who want to evaluate a particular package on Arm.
The Wiki works as follows:
Every package has a page in the packages/ directory. Please feel free to add new pages covering packages we don't yet cover (call them "packages/whatever" to put them in the right directory), and similarly feel free to enhance existing pages with any information you have!
To add a new package to this wiki:
First, please verify that it isn't already present via the All Packages master list below. To add a new package, navigate with your browser to: https://gitlab.com/arm-hpc/packages/wikis/packages/xxxxxx (where xxxxxx is the name of the new HPC package you are adding). This will bring you to a page where you can fill in the initial package info and supply labels/categories appropriately, per labels described below, and then click the "create page" button. Once the All Packages master list refreshes (it updates every few minutes) your new package should show up there. You can further view/edit your package info by clicking on it from the All Packages master list or accessing it directly via the URL you supplied when you added it.
Modifications to these pages cause the project pipeline to run, which regenerates the bottom of this page, and the category pages. When the category lists (including this page) are autogenerated by the Pipeline, only the part within BEGIN/END AUTOGEN comments is affected. This means that you can add Wiki content above or below those sections in the lists (for example, to say something about OpenHPC) and that content will be preserved when the pages are regenerated.
Each package can be categorised, and these lists are auto-generated by a script. See existing pages for how to assign categories to your package. You can use any categories you like - new package lists will be generated automatically.
You can attach labels to packages using the format "Label: key=value" - again, look at existing packages for examples of these.
Please use labels as follows:
Please set to Upstream if an open-source project builds from source on Arm with no modifications (apart from tweaking compiler options for performance). Set to NeedsPatch if patches are required (and please link to those patches!). Set to Supported if a commercial package officially supports 64-bit ARMv8. In the Excel spreadsheet, Upstream and Supported are shown in green, NeedsPatch in amber.
Set to Yes if you have demonstrated that the package compiles with the Arm Compiler (and set BuildMaturity appropriately depending on whether you needed a patch or not). Set to No if you tried and couldn't make it work. Leave this label out if you don't know.
Set to Yes if you have demonstrated that the package compiles with GCC (and set BuildMaturity appropriately depending on whether you needed a patch or not). Set to No if you tried and couldn't make it work. Leave this label out if you don't know.
Set to Yes if there is NEON-specific optimizations in the project. Set to NA if NEON optimisation doesn't make sense for this package. Both are rendered in green in the Excel spreadsheet.