Problem feeding Thrust vector into getrf/getri











up vote
0
down vote

favorite












Continuing on my CUDA beginner's adventure, I've been introduced to Thrust, which seems a convenient lib that saves me the hassle of explicit memory (de-)allocation.



I've already tried combining it with a few cuBLAS routines, e.g. gemv, by generating a raw pointer to the underlying storage with thrust::raw_pointer_cast(array.data()) and then feeding this to the routines, and it works just fine.



The current task is to get the inverse of a matrix, and for that I'm using getrfBatched and getriBatched. From the documentation:



cublasStatus_t cublasDgetrfBatched(cublasHandle_t handle,
int n,
double *Aarray,
int lda,
int *PivotArray,
int *infoArray,
int batchSize);


where



Aarray - device - array of pointers to <type> array


Naturally I thought I could use another layer of Thrust vector to express this array of pointers and again feed its raw pointer to cuBLAS, so here's what I did:



void test()
{
thrust::device_vector<double> in(4);
in[0] = 1;
in[1] = 3;
in[2] = 2;
in[3] = 4;
cublasStatus_t stat;
cublasHandle_t handle;
stat = cublasCreate(&handle);
thrust::device_vector<double> out(4, 0);
thrust::device_vector<int> pivot(2, 0);
int info = 0;
thrust::device_vector<double*> in_array(1);
in_array[0] = thrust::raw_pointer_cast(in.data());
thrust::device_vector<double*> out_array(1);
out_array[0] = thrust::raw_pointer_cast(out.data());
stat = cublasDgetrfBatched(handle, 2,
(double**)thrust::raw_pointer_cast(in_array.data()), 2,
thrust::raw_pointer_cast(pivot.data()), &info, 1);
stat = cublasDgetriBatched(handle, 2,
(const double**)thrust::raw_pointer_cast(in_array.data()), 2,
thrust::raw_pointer_cast(pivot.data()),
(double**)thrust::raw_pointer_cast(out_array.data()), 2, &info, 1);
}


When executed, stat says CUBLAS_STATUS_SUCCESS (0) and info says 0 (execution successful), yet if I try to access the elements of in, pivot or out with standard bracket notation, I hit a thrust::system::system_error. Seems to me that the corresponding memory got corrupted somehow.



Anything obvious that I'm missing here?










share|improve this question


























    up vote
    0
    down vote

    favorite












    Continuing on my CUDA beginner's adventure, I've been introduced to Thrust, which seems a convenient lib that saves me the hassle of explicit memory (de-)allocation.



    I've already tried combining it with a few cuBLAS routines, e.g. gemv, by generating a raw pointer to the underlying storage with thrust::raw_pointer_cast(array.data()) and then feeding this to the routines, and it works just fine.



    The current task is to get the inverse of a matrix, and for that I'm using getrfBatched and getriBatched. From the documentation:



    cublasStatus_t cublasDgetrfBatched(cublasHandle_t handle,
    int n,
    double *Aarray,
    int lda,
    int *PivotArray,
    int *infoArray,
    int batchSize);


    where



    Aarray - device - array of pointers to <type> array


    Naturally I thought I could use another layer of Thrust vector to express this array of pointers and again feed its raw pointer to cuBLAS, so here's what I did:



    void test()
    {
    thrust::device_vector<double> in(4);
    in[0] = 1;
    in[1] = 3;
    in[2] = 2;
    in[3] = 4;
    cublasStatus_t stat;
    cublasHandle_t handle;
    stat = cublasCreate(&handle);
    thrust::device_vector<double> out(4, 0);
    thrust::device_vector<int> pivot(2, 0);
    int info = 0;
    thrust::device_vector<double*> in_array(1);
    in_array[0] = thrust::raw_pointer_cast(in.data());
    thrust::device_vector<double*> out_array(1);
    out_array[0] = thrust::raw_pointer_cast(out.data());
    stat = cublasDgetrfBatched(handle, 2,
    (double**)thrust::raw_pointer_cast(in_array.data()), 2,
    thrust::raw_pointer_cast(pivot.data()), &info, 1);
    stat = cublasDgetriBatched(handle, 2,
    (const double**)thrust::raw_pointer_cast(in_array.data()), 2,
    thrust::raw_pointer_cast(pivot.data()),
    (double**)thrust::raw_pointer_cast(out_array.data()), 2, &info, 1);
    }


    When executed, stat says CUBLAS_STATUS_SUCCESS (0) and info says 0 (execution successful), yet if I try to access the elements of in, pivot or out with standard bracket notation, I hit a thrust::system::system_error. Seems to me that the corresponding memory got corrupted somehow.



    Anything obvious that I'm missing here?










    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      Continuing on my CUDA beginner's adventure, I've been introduced to Thrust, which seems a convenient lib that saves me the hassle of explicit memory (de-)allocation.



      I've already tried combining it with a few cuBLAS routines, e.g. gemv, by generating a raw pointer to the underlying storage with thrust::raw_pointer_cast(array.data()) and then feeding this to the routines, and it works just fine.



      The current task is to get the inverse of a matrix, and for that I'm using getrfBatched and getriBatched. From the documentation:



      cublasStatus_t cublasDgetrfBatched(cublasHandle_t handle,
      int n,
      double *Aarray,
      int lda,
      int *PivotArray,
      int *infoArray,
      int batchSize);


      where



      Aarray - device - array of pointers to <type> array


      Naturally I thought I could use another layer of Thrust vector to express this array of pointers and again feed its raw pointer to cuBLAS, so here's what I did:



      void test()
      {
      thrust::device_vector<double> in(4);
      in[0] = 1;
      in[1] = 3;
      in[2] = 2;
      in[3] = 4;
      cublasStatus_t stat;
      cublasHandle_t handle;
      stat = cublasCreate(&handle);
      thrust::device_vector<double> out(4, 0);
      thrust::device_vector<int> pivot(2, 0);
      int info = 0;
      thrust::device_vector<double*> in_array(1);
      in_array[0] = thrust::raw_pointer_cast(in.data());
      thrust::device_vector<double*> out_array(1);
      out_array[0] = thrust::raw_pointer_cast(out.data());
      stat = cublasDgetrfBatched(handle, 2,
      (double**)thrust::raw_pointer_cast(in_array.data()), 2,
      thrust::raw_pointer_cast(pivot.data()), &info, 1);
      stat = cublasDgetriBatched(handle, 2,
      (const double**)thrust::raw_pointer_cast(in_array.data()), 2,
      thrust::raw_pointer_cast(pivot.data()),
      (double**)thrust::raw_pointer_cast(out_array.data()), 2, &info, 1);
      }


      When executed, stat says CUBLAS_STATUS_SUCCESS (0) and info says 0 (execution successful), yet if I try to access the elements of in, pivot or out with standard bracket notation, I hit a thrust::system::system_error. Seems to me that the corresponding memory got corrupted somehow.



      Anything obvious that I'm missing here?










      share|improve this question













      Continuing on my CUDA beginner's adventure, I've been introduced to Thrust, which seems a convenient lib that saves me the hassle of explicit memory (de-)allocation.



      I've already tried combining it with a few cuBLAS routines, e.g. gemv, by generating a raw pointer to the underlying storage with thrust::raw_pointer_cast(array.data()) and then feeding this to the routines, and it works just fine.



      The current task is to get the inverse of a matrix, and for that I'm using getrfBatched and getriBatched. From the documentation:



      cublasStatus_t cublasDgetrfBatched(cublasHandle_t handle,
      int n,
      double *Aarray,
      int lda,
      int *PivotArray,
      int *infoArray,
      int batchSize);


      where



      Aarray - device - array of pointers to <type> array


      Naturally I thought I could use another layer of Thrust vector to express this array of pointers and again feed its raw pointer to cuBLAS, so here's what I did:



      void test()
      {
      thrust::device_vector<double> in(4);
      in[0] = 1;
      in[1] = 3;
      in[2] = 2;
      in[3] = 4;
      cublasStatus_t stat;
      cublasHandle_t handle;
      stat = cublasCreate(&handle);
      thrust::device_vector<double> out(4, 0);
      thrust::device_vector<int> pivot(2, 0);
      int info = 0;
      thrust::device_vector<double*> in_array(1);
      in_array[0] = thrust::raw_pointer_cast(in.data());
      thrust::device_vector<double*> out_array(1);
      out_array[0] = thrust::raw_pointer_cast(out.data());
      stat = cublasDgetrfBatched(handle, 2,
      (double**)thrust::raw_pointer_cast(in_array.data()), 2,
      thrust::raw_pointer_cast(pivot.data()), &info, 1);
      stat = cublasDgetriBatched(handle, 2,
      (const double**)thrust::raw_pointer_cast(in_array.data()), 2,
      thrust::raw_pointer_cast(pivot.data()),
      (double**)thrust::raw_pointer_cast(out_array.data()), 2, &info, 1);
      }


      When executed, stat says CUBLAS_STATUS_SUCCESS (0) and info says 0 (execution successful), yet if I try to access the elements of in, pivot or out with standard bracket notation, I hit a thrust::system::system_error. Seems to me that the corresponding memory got corrupted somehow.



      Anything obvious that I'm missing here?







      c++ cuda thrust cublas






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 22 at 3:38









      Andy Yan

      1076




      1076
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          2
          down vote



          accepted










          The documentation for cublas<t>getrfBatched indicates that the infoArray parameter is expected to be a pointer to device memory.



          Instead you have passed a pointer to host memory:



          int info = 0;
          ...
          stat = cublasDgetrfBatched(handle, 2,
          (double**)thrust::raw_pointer_cast(in_array.data()), 2,
          thrust::raw_pointer_cast(pivot.data()), &info, 1);
          ^^^^^


          If you run your code with cuda-memcheck (always a good practice, in my opinion, any time you are having trouble with a CUDA code, before asking others for help) you will receive an error of "invalid global write of size 4". This is due to the fact that a kernel launched by cublasDgetrfBatched() is attempting to write the info data to device memory using an ordinary host pointer that you provided, which is always illegal in CUDA.



          CUBLAS itself does not trap errors like this for performance reasons. However the thrust API uses more rigorous synchronization and error checking, in some cases. Therefore, the use of thrust code after this error reports the error, even though the error had nothing to do with thrust (it was an asynchronously reported error from a previous kernel launch).



          The solution is straightforward; provide device storage for info:



          $ cat t329.cu
          #include <thrust/device_vector.h>
          #include <cublas_v2.h>
          #include <iostream>

          void test()
          {
          thrust::device_vector<double> in(4);
          in[0] = 1;
          in[1] = 3;
          in[2] = 2;
          in[3] = 4;
          cublasStatus_t stat;
          cublasHandle_t handle;
          stat = cublasCreate(&handle);
          thrust::device_vector<double> out(4, 0);
          thrust::device_vector<int> pivot(2, 0);
          thrust::device_vector<int> info(1, 0);
          thrust::device_vector<double*> in_array(1);
          in_array[0] = thrust::raw_pointer_cast(in.data());
          thrust::device_vector<double*> out_array(1);
          out_array[0] = thrust::raw_pointer_cast(out.data());
          stat = cublasDgetrfBatched(handle, 2,
          (double**)thrust::raw_pointer_cast(in_array.data()), 2,
          thrust::raw_pointer_cast(pivot.data()), thrust::raw_pointer_cast(info.data()), 1);
          stat = cublasDgetriBatched(handle, 2,
          (const double**)thrust::raw_pointer_cast(in_array.data()), 2,
          thrust::raw_pointer_cast(pivot.data()),
          (double**)thrust::raw_pointer_cast(out_array.data()), 2, thrust::raw_pointer_cast(info.data()), 1);
          for (int i = 0; i < 4; i++) {
          double test = in[i];
          std::cout << test << std::endl;
          }
          }


          int main(){

          test();
          }
          $ nvcc -o t329 t329.cu -lcublas
          t329.cu(12): warning: variable "stat" was set but never used

          $ cuda-memcheck ./t329
          ========= CUDA-MEMCHECK
          3
          0.333333
          4
          0.666667
          ========= ERROR SUMMARY: 0 errors
          $


          You'll note this change in the above code is applied to usage for both cublas calls, as the infoArray parameter has the same expectations for both.






          share|improve this answer























          • Right... Thanks for the helping me a second time!
            – Andy Yan
            Nov 23 at 7:22











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53423540%2fproblem-feeding-thrust-vector-into-getrf-getri%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          2
          down vote



          accepted










          The documentation for cublas<t>getrfBatched indicates that the infoArray parameter is expected to be a pointer to device memory.



          Instead you have passed a pointer to host memory:



          int info = 0;
          ...
          stat = cublasDgetrfBatched(handle, 2,
          (double**)thrust::raw_pointer_cast(in_array.data()), 2,
          thrust::raw_pointer_cast(pivot.data()), &info, 1);
          ^^^^^


          If you run your code with cuda-memcheck (always a good practice, in my opinion, any time you are having trouble with a CUDA code, before asking others for help) you will receive an error of "invalid global write of size 4". This is due to the fact that a kernel launched by cublasDgetrfBatched() is attempting to write the info data to device memory using an ordinary host pointer that you provided, which is always illegal in CUDA.



          CUBLAS itself does not trap errors like this for performance reasons. However the thrust API uses more rigorous synchronization and error checking, in some cases. Therefore, the use of thrust code after this error reports the error, even though the error had nothing to do with thrust (it was an asynchronously reported error from a previous kernel launch).



          The solution is straightforward; provide device storage for info:



          $ cat t329.cu
          #include <thrust/device_vector.h>
          #include <cublas_v2.h>
          #include <iostream>

          void test()
          {
          thrust::device_vector<double> in(4);
          in[0] = 1;
          in[1] = 3;
          in[2] = 2;
          in[3] = 4;
          cublasStatus_t stat;
          cublasHandle_t handle;
          stat = cublasCreate(&handle);
          thrust::device_vector<double> out(4, 0);
          thrust::device_vector<int> pivot(2, 0);
          thrust::device_vector<int> info(1, 0);
          thrust::device_vector<double*> in_array(1);
          in_array[0] = thrust::raw_pointer_cast(in.data());
          thrust::device_vector<double*> out_array(1);
          out_array[0] = thrust::raw_pointer_cast(out.data());
          stat = cublasDgetrfBatched(handle, 2,
          (double**)thrust::raw_pointer_cast(in_array.data()), 2,
          thrust::raw_pointer_cast(pivot.data()), thrust::raw_pointer_cast(info.data()), 1);
          stat = cublasDgetriBatched(handle, 2,
          (const double**)thrust::raw_pointer_cast(in_array.data()), 2,
          thrust::raw_pointer_cast(pivot.data()),
          (double**)thrust::raw_pointer_cast(out_array.data()), 2, thrust::raw_pointer_cast(info.data()), 1);
          for (int i = 0; i < 4; i++) {
          double test = in[i];
          std::cout << test << std::endl;
          }
          }


          int main(){

          test();
          }
          $ nvcc -o t329 t329.cu -lcublas
          t329.cu(12): warning: variable "stat" was set but never used

          $ cuda-memcheck ./t329
          ========= CUDA-MEMCHECK
          3
          0.333333
          4
          0.666667
          ========= ERROR SUMMARY: 0 errors
          $


          You'll note this change in the above code is applied to usage for both cublas calls, as the infoArray parameter has the same expectations for both.






          share|improve this answer























          • Right... Thanks for the helping me a second time!
            – Andy Yan
            Nov 23 at 7:22















          up vote
          2
          down vote



          accepted










          The documentation for cublas<t>getrfBatched indicates that the infoArray parameter is expected to be a pointer to device memory.



          Instead you have passed a pointer to host memory:



          int info = 0;
          ...
          stat = cublasDgetrfBatched(handle, 2,
          (double**)thrust::raw_pointer_cast(in_array.data()), 2,
          thrust::raw_pointer_cast(pivot.data()), &info, 1);
          ^^^^^


          If you run your code with cuda-memcheck (always a good practice, in my opinion, any time you are having trouble with a CUDA code, before asking others for help) you will receive an error of "invalid global write of size 4". This is due to the fact that a kernel launched by cublasDgetrfBatched() is attempting to write the info data to device memory using an ordinary host pointer that you provided, which is always illegal in CUDA.



          CUBLAS itself does not trap errors like this for performance reasons. However the thrust API uses more rigorous synchronization and error checking, in some cases. Therefore, the use of thrust code after this error reports the error, even though the error had nothing to do with thrust (it was an asynchronously reported error from a previous kernel launch).



          The solution is straightforward; provide device storage for info:



          $ cat t329.cu
          #include <thrust/device_vector.h>
          #include <cublas_v2.h>
          #include <iostream>

          void test()
          {
          thrust::device_vector<double> in(4);
          in[0] = 1;
          in[1] = 3;
          in[2] = 2;
          in[3] = 4;
          cublasStatus_t stat;
          cublasHandle_t handle;
          stat = cublasCreate(&handle);
          thrust::device_vector<double> out(4, 0);
          thrust::device_vector<int> pivot(2, 0);
          thrust::device_vector<int> info(1, 0);
          thrust::device_vector<double*> in_array(1);
          in_array[0] = thrust::raw_pointer_cast(in.data());
          thrust::device_vector<double*> out_array(1);
          out_array[0] = thrust::raw_pointer_cast(out.data());
          stat = cublasDgetrfBatched(handle, 2,
          (double**)thrust::raw_pointer_cast(in_array.data()), 2,
          thrust::raw_pointer_cast(pivot.data()), thrust::raw_pointer_cast(info.data()), 1);
          stat = cublasDgetriBatched(handle, 2,
          (const double**)thrust::raw_pointer_cast(in_array.data()), 2,
          thrust::raw_pointer_cast(pivot.data()),
          (double**)thrust::raw_pointer_cast(out_array.data()), 2, thrust::raw_pointer_cast(info.data()), 1);
          for (int i = 0; i < 4; i++) {
          double test = in[i];
          std::cout << test << std::endl;
          }
          }


          int main(){

          test();
          }
          $ nvcc -o t329 t329.cu -lcublas
          t329.cu(12): warning: variable "stat" was set but never used

          $ cuda-memcheck ./t329
          ========= CUDA-MEMCHECK
          3
          0.333333
          4
          0.666667
          ========= ERROR SUMMARY: 0 errors
          $


          You'll note this change in the above code is applied to usage for both cublas calls, as the infoArray parameter has the same expectations for both.






          share|improve this answer























          • Right... Thanks for the helping me a second time!
            – Andy Yan
            Nov 23 at 7:22













          up vote
          2
          down vote



          accepted







          up vote
          2
          down vote



          accepted






          The documentation for cublas<t>getrfBatched indicates that the infoArray parameter is expected to be a pointer to device memory.



          Instead you have passed a pointer to host memory:



          int info = 0;
          ...
          stat = cublasDgetrfBatched(handle, 2,
          (double**)thrust::raw_pointer_cast(in_array.data()), 2,
          thrust::raw_pointer_cast(pivot.data()), &info, 1);
          ^^^^^


          If you run your code with cuda-memcheck (always a good practice, in my opinion, any time you are having trouble with a CUDA code, before asking others for help) you will receive an error of "invalid global write of size 4". This is due to the fact that a kernel launched by cublasDgetrfBatched() is attempting to write the info data to device memory using an ordinary host pointer that you provided, which is always illegal in CUDA.



          CUBLAS itself does not trap errors like this for performance reasons. However the thrust API uses more rigorous synchronization and error checking, in some cases. Therefore, the use of thrust code after this error reports the error, even though the error had nothing to do with thrust (it was an asynchronously reported error from a previous kernel launch).



          The solution is straightforward; provide device storage for info:



          $ cat t329.cu
          #include <thrust/device_vector.h>
          #include <cublas_v2.h>
          #include <iostream>

          void test()
          {
          thrust::device_vector<double> in(4);
          in[0] = 1;
          in[1] = 3;
          in[2] = 2;
          in[3] = 4;
          cublasStatus_t stat;
          cublasHandle_t handle;
          stat = cublasCreate(&handle);
          thrust::device_vector<double> out(4, 0);
          thrust::device_vector<int> pivot(2, 0);
          thrust::device_vector<int> info(1, 0);
          thrust::device_vector<double*> in_array(1);
          in_array[0] = thrust::raw_pointer_cast(in.data());
          thrust::device_vector<double*> out_array(1);
          out_array[0] = thrust::raw_pointer_cast(out.data());
          stat = cublasDgetrfBatched(handle, 2,
          (double**)thrust::raw_pointer_cast(in_array.data()), 2,
          thrust::raw_pointer_cast(pivot.data()), thrust::raw_pointer_cast(info.data()), 1);
          stat = cublasDgetriBatched(handle, 2,
          (const double**)thrust::raw_pointer_cast(in_array.data()), 2,
          thrust::raw_pointer_cast(pivot.data()),
          (double**)thrust::raw_pointer_cast(out_array.data()), 2, thrust::raw_pointer_cast(info.data()), 1);
          for (int i = 0; i < 4; i++) {
          double test = in[i];
          std::cout << test << std::endl;
          }
          }


          int main(){

          test();
          }
          $ nvcc -o t329 t329.cu -lcublas
          t329.cu(12): warning: variable "stat" was set but never used

          $ cuda-memcheck ./t329
          ========= CUDA-MEMCHECK
          3
          0.333333
          4
          0.666667
          ========= ERROR SUMMARY: 0 errors
          $


          You'll note this change in the above code is applied to usage for both cublas calls, as the infoArray parameter has the same expectations for both.






          share|improve this answer














          The documentation for cublas<t>getrfBatched indicates that the infoArray parameter is expected to be a pointer to device memory.



          Instead you have passed a pointer to host memory:



          int info = 0;
          ...
          stat = cublasDgetrfBatched(handle, 2,
          (double**)thrust::raw_pointer_cast(in_array.data()), 2,
          thrust::raw_pointer_cast(pivot.data()), &info, 1);
          ^^^^^


          If you run your code with cuda-memcheck (always a good practice, in my opinion, any time you are having trouble with a CUDA code, before asking others for help) you will receive an error of "invalid global write of size 4". This is due to the fact that a kernel launched by cublasDgetrfBatched() is attempting to write the info data to device memory using an ordinary host pointer that you provided, which is always illegal in CUDA.



          CUBLAS itself does not trap errors like this for performance reasons. However the thrust API uses more rigorous synchronization and error checking, in some cases. Therefore, the use of thrust code after this error reports the error, even though the error had nothing to do with thrust (it was an asynchronously reported error from a previous kernel launch).



          The solution is straightforward; provide device storage for info:



          $ cat t329.cu
          #include <thrust/device_vector.h>
          #include <cublas_v2.h>
          #include <iostream>

          void test()
          {
          thrust::device_vector<double> in(4);
          in[0] = 1;
          in[1] = 3;
          in[2] = 2;
          in[3] = 4;
          cublasStatus_t stat;
          cublasHandle_t handle;
          stat = cublasCreate(&handle);
          thrust::device_vector<double> out(4, 0);
          thrust::device_vector<int> pivot(2, 0);
          thrust::device_vector<int> info(1, 0);
          thrust::device_vector<double*> in_array(1);
          in_array[0] = thrust::raw_pointer_cast(in.data());
          thrust::device_vector<double*> out_array(1);
          out_array[0] = thrust::raw_pointer_cast(out.data());
          stat = cublasDgetrfBatched(handle, 2,
          (double**)thrust::raw_pointer_cast(in_array.data()), 2,
          thrust::raw_pointer_cast(pivot.data()), thrust::raw_pointer_cast(info.data()), 1);
          stat = cublasDgetriBatched(handle, 2,
          (const double**)thrust::raw_pointer_cast(in_array.data()), 2,
          thrust::raw_pointer_cast(pivot.data()),
          (double**)thrust::raw_pointer_cast(out_array.data()), 2, thrust::raw_pointer_cast(info.data()), 1);
          for (int i = 0; i < 4; i++) {
          double test = in[i];
          std::cout << test << std::endl;
          }
          }


          int main(){

          test();
          }
          $ nvcc -o t329 t329.cu -lcublas
          t329.cu(12): warning: variable "stat" was set but never used

          $ cuda-memcheck ./t329
          ========= CUDA-MEMCHECK
          3
          0.333333
          4
          0.666667
          ========= ERROR SUMMARY: 0 errors
          $


          You'll note this change in the above code is applied to usage for both cublas calls, as the infoArray parameter has the same expectations for both.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 23 at 5:44

























          answered Nov 23 at 5:39









          Robert Crovella

          93.1k4101143




          93.1k4101143












          • Right... Thanks for the helping me a second time!
            – Andy Yan
            Nov 23 at 7:22


















          • Right... Thanks for the helping me a second time!
            – Andy Yan
            Nov 23 at 7:22
















          Right... Thanks for the helping me a second time!
          – Andy Yan
          Nov 23 at 7:22




          Right... Thanks for the helping me a second time!
          – Andy Yan
          Nov 23 at 7:22


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53423540%2fproblem-feeding-thrust-vector-into-getrf-getri%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          What visual should I use to simply compare current year value vs last year in Power BI desktop

          How to ignore python UserWarning in pytest?

          Alexandru Averescu