Skip to content

Latest commit

 

History

History
88 lines (75 loc) · 6.23 KB

SOURCEINSTALL.md

File metadata and controls

88 lines (75 loc) · 6.23 KB
Raw

Source Install V 20.0-1

Build and install from sources is possible. However, the source build for AOMP is complex for several reasons.

  • Many repos are required.
  • Requires that Cuda SDK 10 is installed for NVIDIA GPUs. ROCm does not need to be installed for AOMP.
  • It is a bootstrapped build. The built and installed LLVM compiler is used to build library components.
  • Additional package dependencies are required that are not required when installing the AOMP package.

Source Build Prerequisites

To build and test AOMP from source you must:

1. Install certain distribution packages,
2. Build CMake 3.22.1 from source. This can be done with ./build_prereq.sh,
3. Ensure the KFD kernel module is installed and operating,
4. Create the Unix video group, and
5. Install spack if required.

This link provides detailed instructions to satisfy all the AOMP source build requirements.

Clone and Build AOMP

AOMP now uses a manifest file to specify the git repositories to clone. We studied the use of the google repo command and found it was too compilicated for development as compared to manually cloning the repos specified in a manifest file. The script clone_aomp.sh issues a sequence of "git clone" and "git pull" commands by parsing information in the manifest file associated with a particular release.

Choose a Build Version (Development or Release) The development version is the next version to be released. It is possible that the development version is broken due to regressions that often occur during development.

Here are the commands to do a source build of AOMP:

Development Branch:

   export AOMP_VERSION=20.0
   export AOMP_REPOS=$HOME/git/aomp${AOMP_VERSION}
   mkdir -p $AOMP_REPOS
   cd $AOMP_REPOS
   git clone -b aomp-dev https://github.com/ROCm-Developer-Tools/aomp

The development version is the next version to be released. It is possible that the development version is broken due to regressions that often occur during development. These commands will build a previous release of AOMP such as aomp-20.0-0.
Release Branch:

   export AOMP_VERSION=20.0
   export AOMP_REPOS=$HOME/git/aomp${AOMP_VERSION}
   mkdir -p $AOMP_REPOS
   cd $AOMP_REPOS
   git clone -b aomp-20.0-0 https://github.com/ROCm-Developer-Tools/aomp

Clone and build:

   $AOMP_REPOS/aomp/bin/clone_aomp.sh
   $AOMP_REPOS/aomp/bin/build_prereq.sh
   nohup $AOMP_REPOS/aomp/bin/build_aomp.sh &

Change the value of AOMP_REPOS to the directory name where you want to store all the repositories needed for AOMP. All the AOMP repositories will consume more than 12GB. Furthermore, each AOMP component will be built in a subdirectory of $AOMP_REPOS/build which will consume an additional 6GB. So it is recommened that the directory $AOMP_REPOS have more than 20GB of free space before beginning. It is recommended that $AOMP_REPOS name include the value of AOMP_VERSION as shown above. It is also recommended to put the values of AOMP_VERSION and AOMP_REPOS in a login profile (such as .bashrc) so future incremental build scripts will correctly find your sources.

Warning: the clone_aomp.sh, and build_aomp.sh are expected to take a long time to execute. As such we recommend the use of nohup to run build_aomp.sh. It is ok to run build_aomp.sh without nohup. The clone and build time will be affected by the performance of the filesystem that contains $AOMP_REPOS.

There is a "list" option on the clone_aomp.sh that provides useful information about each AOMP repository.

   $AOMP_REPOS/aomp/bin/clone_aomp.sh list

The above command will produce output like this showing you the location and branch of the repos in the AOMP_REPOS directory and if there are any discrepencies with respect to the manifest file.

USED manifest file: /work/grodgers/git/aomp20.0/aomp/bin/../manifests/aompi_20.0.xml
repo src branch path repo name last hash updated commitor for author

gerritgit amd-staging llvm-project lightning/ec/llvm-project f986706166c9 2023-12-06 Ron Lieberman JP Lehr roctools aomp-dev flang flang 88b81b0a8ead 2023-11-30 GitHub Emma Pilkington roctools aomp-dev aomp-extras aomp-extras 7097f3e2ba36 2023-12-04 Ron Lieberman Ron Lieberman roctools aomp-dev aomp aomp df5b5d8ddffa 2023-12-05 Dhruva Chakrabarti Dhruva Chakrabarti roctools rocm-6.2.x rocprofiler rocprofiler 4e190a02e60e 2023-10-30 GitHub Ammar ELWazir roctools rocm-6.2.x roctracer roctracer 6fbf7673aa7f 2023-07-13 Ranjith Ramakrishnan Ranjith Ramakrishnan roctools rocm-6.2.x ROCdbgapi ROCdbgapi df1a8df2be08 2023-07-28 Lancelot SIX Lancelot SIX roctools rocm-6.2.x ROCgdb ROCgdb 157eed788288 2023-07-28 Lancelot SIX Lancelot SIX roctools rocm-6.2.x hip hip 80681169ae20 2023-08-15 Julia Jiang Julia Jiang roctools rocm-6.2.x clr clr 1949b1621a80 2023-09-21 Julia Jiang Julia Jiang roc rocm-6.2.x rocminfo rocminfo c8db38ede264 2023-06-02 Mark Searles Mark Searles roc rocm-rel-6.2 rocm-cmake rocm-cmake 15cbb2e47f0b 2023-07-11 Lauren Wrubleski Lauren Wrubleski roc rocm-6.2.x rocr-runtime ROCR-Runtime b2b6811571bf 2023-09-15 David Yat Sin David Yat Sin roc rocm-6.2.x roct-thunk-interface ROCT-Thunk-Interface 5268ea80e32a 2023-08-09 David Belanger David Belanger rocsw rocm-rel-6.2 hipfort hipfort 41f33eeaa3f7 2023-09-07 Sam Wu dependabot[bot]

For more information, or if you are interested in joining the development of AOMP, please read the AOMP developers README file located here [README](../bin/README.md).