Skip to content

Latest commit

 

History

History
136 lines (99 loc) · 5.48 KB

README.md

File metadata and controls

136 lines (99 loc) · 5.48 KB
Raw
 _ ) |      \    __|    |     |
 _ \ |     _ \ \__ \ __ __|__ __|
___/____|_/  _\____/   _|    _|

C++ API for the Basic Linear Algebra Subroutines

Innovative Computing Laboratory

University of Tennessee

[TOC]

About

The Basic Linear Algebra Subprograms (BLAS) have been around for many decades and serve as the de facto standard for performance-portable and numerically robust implementation of essential linear algebra functionality. Originally, they were written in Fortran, and later furnished with a C API (CBLAS).

The objective of BLAS++ is to provide a convenient, performance oriented API for development in the C++ language, that, for the most part, preserves established conventions, while, at the same time, takes advantages of modern C++ features, such as: namespaces, templates, exceptions, etc.

BLAS++ is part of the SLATE project (Software for Linear Algebra Targeting Exascale), which is funded by the Department of Energy as part of its Exascale Computing Initiative (ECP). Closely related to BLAS++ is the LAPACK++ project, which provides a C++ API for LAPACK.

BLASPP

Documentation

Getting Help

For assistance, visit the SLATE User Forum at https://groups.google.com/a/icl.utk.edu/forum/#!forum/slate-user. Join by signing in with your Google credentials, then clicking Join group to post.

Bug reports can be filed directly on Bitbucket's issue tracker: https://bitbucket.org/icl/blaspp/issues?status=new&status=open.

Resources

  • Visit the LAPACK++ repository for more information about the C++ API for LAPACK.
  • Visit the SLATE website for more information about the SLATE project.
  • Visit the SLATE Working Notes to find out more about ongoing SLATE developments.
  • Visit the ECP website to find out more about the DOE Exascale Computing Initiative.

Contributing

The SLATE project welcomes contributions from new developers. Contributions can be offered through the standard Bitbucket pull request model. We strongly encourage you to coordinate large contributions with the SLATE development team early in the process.

Acknowledgments

This research was supported by the Exascale Computing Project (17-SC-20-SC), a joint project of the U.S. Department of Energy's Office of Science and National Nuclear Security Administration, responsible for delivering a capable exascale ecosystem, including software, applications, and hardware technology, to support the nation’s exascale computing imperative.

This research uses resources of the Oak Ridge Leadership Computing Facility, which is a DOE Office of Science User Facility supported under Contract DE-AC05-00OR22725. This research also uses resources of the Argonne Leadership Computing Facility, which is a DOE Office of Science User Facility supported under Contract DE-AC02-06CH11357.

License

Copyright (c) 2017-2022, University of Tennessee. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

  • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

  • Neither the name of the University of Tennessee nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

This software is provided by the copyright holders and contributors "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the copyright holders or contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.