Calling ipp functions corrupts variables





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I have picked up coding with IPP again after some time and an update from windows 7 to windows 10. But now it seems to corrupt the value of variables when I can an ipp malloc function.



For instance this code:






#include <stdio.h>
#include "ipp.h"


int main(void)
{
IppiSize roiSize = {128,128};
IppiSize kernelSize= {3,3};
int srcStep = 0;
Ipp8u* pSrc = NULL;

printf("%d %d n", roiSize.width, roiSize.height);
printf("%d %d n", kernelSize.width, kernelSize.height);

pSrc = ippsMalloc_8u(0);

printf("%d %d n", roiSize.width, roiSize.height);
printf("%d %d n", kernelSize.width, kernelSize.height);
return 0;
}





returns:






 
128 128
3 3
128 0
3 128





so it modifies the value of roiSize and kernelSize even though it's not intended to. A standard C malloc works fine and dose not corrupt the variables.
I compiled (without any warning) with cygwin x86 gcc 7.4.0, on windows 10 pro version 1709, using






HDIR = "C:Program Files (x86)IntelSWToolscompilers_and_libraries_2019.1.144windowsippinclude"
LDADD = "C:Program Files (x86)IntelSWToolscompilers_and_libraries_2019.1.144windowsredistia32_winipp" -lippi -lipps -lippvm -lippcore -lippvm -lm
CXXFLAGS = -O0
SOURCES= test.cpp
OBJECTS1=$(patsubst %.cpp,%.o,$(SOURCES))
OBJECTS=$(patsubst %.c,%.o,$(OBJECTS1))

all debug profile static depend: $(OBJECTS)
g++ -o test.exe test.o $(CXXFLAGS) -L$(LDADD)


%.o: %.cpp
g++ -c $< $(CXXFLAGS) -I $(HDIR)

%.o: %.c
g++ -c $< $(CXXFLAGS) -I $(HDIR)

clean:
rm -f *.o





Anybody has already seen anything like this? I'm at a loss to find the root cause of the issue.










share|improve this question































    0















    I have picked up coding with IPP again after some time and an update from windows 7 to windows 10. But now it seems to corrupt the value of variables when I can an ipp malloc function.



    For instance this code:






    #include <stdio.h>
    #include "ipp.h"


    int main(void)
    {
    IppiSize roiSize = {128,128};
    IppiSize kernelSize= {3,3};
    int srcStep = 0;
    Ipp8u* pSrc = NULL;

    printf("%d %d n", roiSize.width, roiSize.height);
    printf("%d %d n", kernelSize.width, kernelSize.height);

    pSrc = ippsMalloc_8u(0);

    printf("%d %d n", roiSize.width, roiSize.height);
    printf("%d %d n", kernelSize.width, kernelSize.height);
    return 0;
    }





    returns:






     
    128 128
    3 3
    128 0
    3 128





    so it modifies the value of roiSize and kernelSize even though it's not intended to. A standard C malloc works fine and dose not corrupt the variables.
    I compiled (without any warning) with cygwin x86 gcc 7.4.0, on windows 10 pro version 1709, using






    HDIR = "C:Program Files (x86)IntelSWToolscompilers_and_libraries_2019.1.144windowsippinclude"
    LDADD = "C:Program Files (x86)IntelSWToolscompilers_and_libraries_2019.1.144windowsredistia32_winipp" -lippi -lipps -lippvm -lippcore -lippvm -lm
    CXXFLAGS = -O0
    SOURCES= test.cpp
    OBJECTS1=$(patsubst %.cpp,%.o,$(SOURCES))
    OBJECTS=$(patsubst %.c,%.o,$(OBJECTS1))

    all debug profile static depend: $(OBJECTS)
    g++ -o test.exe test.o $(CXXFLAGS) -L$(LDADD)


    %.o: %.cpp
    g++ -c $< $(CXXFLAGS) -I $(HDIR)

    %.o: %.c
    g++ -c $< $(CXXFLAGS) -I $(HDIR)

    clean:
    rm -f *.o





    Anybody has already seen anything like this? I'm at a loss to find the root cause of the issue.










    share|improve this question



























      0












      0








      0








      I have picked up coding with IPP again after some time and an update from windows 7 to windows 10. But now it seems to corrupt the value of variables when I can an ipp malloc function.



      For instance this code:






      #include <stdio.h>
      #include "ipp.h"


      int main(void)
      {
      IppiSize roiSize = {128,128};
      IppiSize kernelSize= {3,3};
      int srcStep = 0;
      Ipp8u* pSrc = NULL;

      printf("%d %d n", roiSize.width, roiSize.height);
      printf("%d %d n", kernelSize.width, kernelSize.height);

      pSrc = ippsMalloc_8u(0);

      printf("%d %d n", roiSize.width, roiSize.height);
      printf("%d %d n", kernelSize.width, kernelSize.height);
      return 0;
      }





      returns:






       
      128 128
      3 3
      128 0
      3 128





      so it modifies the value of roiSize and kernelSize even though it's not intended to. A standard C malloc works fine and dose not corrupt the variables.
      I compiled (without any warning) with cygwin x86 gcc 7.4.0, on windows 10 pro version 1709, using






      HDIR = "C:Program Files (x86)IntelSWToolscompilers_and_libraries_2019.1.144windowsippinclude"
      LDADD = "C:Program Files (x86)IntelSWToolscompilers_and_libraries_2019.1.144windowsredistia32_winipp" -lippi -lipps -lippvm -lippcore -lippvm -lm
      CXXFLAGS = -O0
      SOURCES= test.cpp
      OBJECTS1=$(patsubst %.cpp,%.o,$(SOURCES))
      OBJECTS=$(patsubst %.c,%.o,$(OBJECTS1))

      all debug profile static depend: $(OBJECTS)
      g++ -o test.exe test.o $(CXXFLAGS) -L$(LDADD)


      %.o: %.cpp
      g++ -c $< $(CXXFLAGS) -I $(HDIR)

      %.o: %.c
      g++ -c $< $(CXXFLAGS) -I $(HDIR)

      clean:
      rm -f *.o





      Anybody has already seen anything like this? I'm at a loss to find the root cause of the issue.










      share|improve this question
















      I have picked up coding with IPP again after some time and an update from windows 7 to windows 10. But now it seems to corrupt the value of variables when I can an ipp malloc function.



      For instance this code:






      #include <stdio.h>
      #include "ipp.h"


      int main(void)
      {
      IppiSize roiSize = {128,128};
      IppiSize kernelSize= {3,3};
      int srcStep = 0;
      Ipp8u* pSrc = NULL;

      printf("%d %d n", roiSize.width, roiSize.height);
      printf("%d %d n", kernelSize.width, kernelSize.height);

      pSrc = ippsMalloc_8u(0);

      printf("%d %d n", roiSize.width, roiSize.height);
      printf("%d %d n", kernelSize.width, kernelSize.height);
      return 0;
      }





      returns:






       
      128 128
      3 3
      128 0
      3 128





      so it modifies the value of roiSize and kernelSize even though it's not intended to. A standard C malloc works fine and dose not corrupt the variables.
      I compiled (without any warning) with cygwin x86 gcc 7.4.0, on windows 10 pro version 1709, using






      HDIR = "C:Program Files (x86)IntelSWToolscompilers_and_libraries_2019.1.144windowsippinclude"
      LDADD = "C:Program Files (x86)IntelSWToolscompilers_and_libraries_2019.1.144windowsredistia32_winipp" -lippi -lipps -lippvm -lippcore -lippvm -lm
      CXXFLAGS = -O0
      SOURCES= test.cpp
      OBJECTS1=$(patsubst %.cpp,%.o,$(SOURCES))
      OBJECTS=$(patsubst %.c,%.o,$(OBJECTS1))

      all debug profile static depend: $(OBJECTS)
      g++ -o test.exe test.o $(CXXFLAGS) -L$(LDADD)


      %.o: %.cpp
      g++ -c $< $(CXXFLAGS) -I $(HDIR)

      %.o: %.c
      g++ -c $< $(CXXFLAGS) -I $(HDIR)

      clean:
      rm -f *.o





      Anybody has already seen anything like this? I'm at a loss to find the root cause of the issue.






      #include <stdio.h>
      #include "ipp.h"


      int main(void)
      {
      IppiSize roiSize = {128,128};
      IppiSize kernelSize= {3,3};
      int srcStep = 0;
      Ipp8u* pSrc = NULL;

      printf("%d %d n", roiSize.width, roiSize.height);
      printf("%d %d n", kernelSize.width, kernelSize.height);

      pSrc = ippsMalloc_8u(0);

      printf("%d %d n", roiSize.width, roiSize.height);
      printf("%d %d n", kernelSize.width, kernelSize.height);
      return 0;
      }





      #include <stdio.h>
      #include "ipp.h"


      int main(void)
      {
      IppiSize roiSize = {128,128};
      IppiSize kernelSize= {3,3};
      int srcStep = 0;
      Ipp8u* pSrc = NULL;

      printf("%d %d n", roiSize.width, roiSize.height);
      printf("%d %d n", kernelSize.width, kernelSize.height);

      pSrc = ippsMalloc_8u(0);

      printf("%d %d n", roiSize.width, roiSize.height);
      printf("%d %d n", kernelSize.width, kernelSize.height);
      return 0;
      }





       
      128 128
      3 3
      128 0
      3 128





       
      128 128
      3 3
      128 0
      3 128





      HDIR = "C:Program Files (x86)IntelSWToolscompilers_and_libraries_2019.1.144windowsippinclude"
      LDADD = "C:Program Files (x86)IntelSWToolscompilers_and_libraries_2019.1.144windowsredistia32_winipp" -lippi -lipps -lippvm -lippcore -lippvm -lm
      CXXFLAGS = -O0
      SOURCES= test.cpp
      OBJECTS1=$(patsubst %.cpp,%.o,$(SOURCES))
      OBJECTS=$(patsubst %.c,%.o,$(OBJECTS1))

      all debug profile static depend: $(OBJECTS)
      g++ -o test.exe test.o $(CXXFLAGS) -L$(LDADD)


      %.o: %.cpp
      g++ -c $< $(CXXFLAGS) -I $(HDIR)

      %.o: %.c
      g++ -c $< $(CXXFLAGS) -I $(HDIR)

      clean:
      rm -f *.o





      HDIR = "C:Program Files (x86)IntelSWToolscompilers_and_libraries_2019.1.144windowsippinclude"
      LDADD = "C:Program Files (x86)IntelSWToolscompilers_and_libraries_2019.1.144windowsredistia32_winipp" -lippi -lipps -lippvm -lippcore -lippvm -lm
      CXXFLAGS = -O0
      SOURCES= test.cpp
      OBJECTS1=$(patsubst %.cpp,%.o,$(SOURCES))
      OBJECTS=$(patsubst %.c,%.o,$(OBJECTS1))

      all debug profile static depend: $(OBJECTS)
      g++ -o test.exe test.o $(CXXFLAGS) -L$(LDADD)


      %.o: %.cpp
      g++ -c $< $(CXXFLAGS) -I $(HDIR)

      %.o: %.c
      g++ -c $< $(CXXFLAGS) -I $(HDIR)

      clean:
      rm -f *.o






      intel-ipp






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 3 at 16:12







      cm69

















      asked Jan 3 at 16:06









      cm69cm69

      12




      12
























          0






          active

          oldest

          votes












          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',
          autoActivateHeartbeat: false,
          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%2f54025896%2fcalling-ipp-functions-corrupts-variables%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          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.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54025896%2fcalling-ipp-functions-corrupts-variables%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

          MongoDB - Not Authorized To Execute Command

          How to fix TextFormField cause rebuild widget in Flutter

          Npm cannot find a required file even through it is in the searched directory