Compiler Flags
Compiler flags
[Intel Compilers | Gnu Compiler Collection (GCC) Compilers | Portland Group (PGI) Compilers ]
[Intel Compilers | Gnu Compiler Collection (GCC) Compilers | Portland Group (PGI) Compilers ]
[GNU Compiler Collection (GCC) Compilers | Intel Compilers | PathScale Compilers | Portland Group (PGI) Compilers ]
Compilers are preferrably loaded as part of compiler toolchains. Read our page "Installed Compilers" for more about that.
To list all compiler toolchains, either do
module avail
or
This section provides information about the compilers at HPC2N. There are instructions about their usage, and some of the most popular flags, as well as the provided libraries and how to link to them.
There is also a section with an introduction to makefiles, a few examples, and links to more information.
There are several possible ways to transfer files and data to and from HPC2N's systems.
There are a number of options for archiving and compressing directories and files at HPC2N.
[ Overview | $HOME | Project storage | /scratch | SweStore ]
This section provides information about the file systems at HPC2N. Since your home directory is per default quite small, you should keep files needed for your jobs in your project storage. Read more on the 'File system/Storage' page.
There is also a short description of the most common environment variables, as well as instructions on how to compress and archive your data and other files.
This page is assuming you use bash or another shell in the Bourne family of shells. Most of the informtation will be correct for other shells as well, but the examples cannot be assumed to be.
HPC2N recommends using bash, since it is the only shell that is fully supported by the batch system.
Environment variables are a set of dynamic named values, generally meant to make your life easier. Some are built-in, some are set by loading various modules, and you can also define extra to help yourself.