8000 Remove Xpetra warnings when compiling for CUDA · Issue #1148 · trilinos/Trilinos · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Remove Xpetra warnings when compiling for CUDA #1148

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jhux2 opened this issue Mar 17, 2017 · 5 comments
Closed

Remove Xpetra warnings when compiling for CUDA #1148

jhux2 opened this issue Mar 17, 2017 · 5 comments
Labels
impacting: configure or build The issue is primarily related to configuring or building pkg: Xpetra

Comments

@jhux2
Copy link
Member
jhux2 commented Mar 17, 2017

We can use the macro TEUCHOS_NONREACHABLE_RETURN(RETURN_VAL) as in issue #1140 to get rid of warnings like

Trilinos_apollo_gcc_4.8.4_cuda_7.5.18/MPI_RELEASE_DEV_DownStream_ETI_SERIAL-ON_OPENMP-OFF_PTHREAD-OFF_CUDA-ON_COMPLEX-OFF/Trilinos/packages/xpetra/src/Map/Xpetra_EpetraMap.hpp(655): warning: statement is unreachable
@jhux2 jhux2 added impacting: configure or build The issue is primarily related to configuring or building pkg: Xpetra labels Mar 17, 2017
@jhux2
Copy link
Member Author
jhux2 commented Mar 17, 2017

@trilinos/xpetra

@jhux2
Copy link
Member Author
jhux2 commented Mar 17, 2017

Examples here.

@aprokop
Copy link
Contributor
aprokop commented Mar 17, 2017

So, does it work for all compilers? Different compilers produce different warnings?

@jhux2
Copy link
Member Author
jhux2 commented Mar 17, 2017

So, does it work for all compilers? Different compilers produce different warnings?

I think this is just meant to address the particular CUDA warning statement is unreachable.

jhux2 added a commit that referenced this issue Aug 3, 2017
To address issues #1148 and #1133.

Build/Test Cases Summary
Enabled Packages: Xpetra
Disabled Packages: PyTrilinos,Claps,TriKota
Enabled all Forward Packages
0) MPI_RELEASE_DEBUG_SHARED_PT => passed: passed=585,notpassed=0 (120.09 min)
jhux2 added a commit that referenced this issue Aug 4, 2017
To eliminate "warning: dynamic initialization in unreachable code".
See github issues #1133 and #1148.

Build/Test Cases Summary
Enabled Packages: MueLu, Xpetra
Disabled Packages: PyTrilinos,Claps,TriKota
Enabled all Forward Packages
0) MPI_RELEASE_DEBUG_SHARED_PT => passed: passed=585,notpassed=0 (103.63 min)
Other local commits for this build/test group: 5470ba5, ae1c06a
lxmota pushed a commit that referenced this issue Aug 8, 2017
To address issues #1148 and #1133.

Build/Test Cases Summary
Enabled Packages: Xpetra
Disabled Packages: PyTrilinos,Claps,TriKota
Enabled all Forward Packages
0) MPI_RELEASE_DEBUG_SHARED_PT => passed: passed=585,notpassed=0 (120.09 min)
lxmota pushed a commit that referenced this issue Aug 8, 2017
To eliminate "warning: dynamic initialization in unreachable code".
See github issues #1133 and #1148.

Build/Test Cases Summary
Enabled Packages: MueLu, Xpetra
Disabled Packages: PyTrilinos,Claps,TriKota
Enabled all Forward Packages
0) MPI_RELEASE_DEBUG_SHARED_PT => passed: passed=585,notpassed=0 (103.63 min)
Other local commits for this build/test group: 5470ba5, ae1c06a
crtrott pushed a commit to mndevec/Trilinos that referenced this issue Aug 17, 2017
To eliminate "warning: dynamic initialization in unreachable code".
See github issues trilinos#1133 and trilinos#1148.

Build/Test Cases Summary
Enabled Packages: MueLu, Xpetra
Disabled Packages: PyTrilinos,Claps,TriKota
Enabled all Forward Packages
0) MPI_RELEASE_DEBUG_SHARED_PT => passed: passed=585,notpassed=0 (103.63 min)
Other local commits for this build/test group: 5470ba5, ae1c06a
@jhux2
Copy link
Member Author
jhux2 commented Jun 14, 2018

Closing, as these warnings have been addressed.

@jhux2 jhux2 closed this as completed Jun 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impacting: configure or build The issue is primarily related to configuring or building pkg: Xpetra
Projects
None yet
Development

No branches or pull requests

2 participants
0