Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Trilinos
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 936
    • Issues 936
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • James Willenbring
  • Trilinos
  • Merge requests
  • !4701

Merged
Created Mar 22, 2019 by James Willenbring@jmwilleMaintainer4 of 9 tasks completed4/9 tasks

Tpetra: Deprecate DynamicProfile

  • Overview 45
  • Commits 15
  • Changes 17

Created by: GeoffDanielson

@trilinos/tpetra

Description

This uses the TPETRA_ENABLE_DEPRECATED_CODE macro to switch the default constructors in CrsGraph and CrsMatrix to use StaticProfile as default, and warn of profileTypes upcoming deprecation

Motivation and Context

This brings us one step closer to static allocation for GPU usage.

How Has This Been Tested?

This was tested by building the tpetra package and building its tests both with and without the TPETRA_ENABLE_DEPRECATED_CODE macro enabled.

The non-GCC guarded portions (for Intel compilers) remains untested, because I don't have a machine with an intel compiler new enough. However, GCC works on the pragma messages alone (I called out the pragma warning specific to the GCC compiler because warnings are more appropriate to the issue than simple messages). It may be that the Intel compiler will support pragma warnings as well, but I figured I would stick with the universally supported macros.

Checklist

  • My commit messages mention the appropriate GitHub issue numbers.
  • My code follows the code style of the affected package(s).
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the code contribution guidelines for this project.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • No new compiler warnings were introduced.
  • These changes break backwards compatibility.

Additional Information

This introduces new compiler warnings, on purpose (the entire point was to introduce compiler warnings).

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: minor_tpetra_deprecation