General Manager at a manufacturing company with 10,001+ employees
Real User
Top 20
Oct 9, 2025
Execution speed of the tests and generally the integration into AWS-driven CI work chains or workflows represent how it can be improved in my opinion. Performance issues plus license costs are two main driving factors. The CI environments that we use employ up to around 40,000 virtual CPUs per day in peak, running at the same time. We always have problems distributing licenses accordingly with other products. I can talk to the experts doing the integration, but as far as I know, I was involved with Polyspace Code Prover and we had a lot of difficulties integrating it into our Bazel-driven CI toolchain, plus integrating it on the AWS environments in Linux that we use. It was much more straightforward using Code Sonar there. The reason is the execution speed, integration with Azure and stuff, and pricing. The CI integration and maybe a better-suited license model for CI-driven execution are other areas I recommend improving. That's something we discussed with all of the software companies whose products we use, such as compilers. We have a lot of parallel builds, and each call to a license server is actually problematic in the long run.
Software Engineer at Federal University of Minas Gerais
Real User
Top 20
Aug 14, 2024
I'm still trying to use constraints with range propagation, but I can't get it to work properly, and I haven't found any documentation. It require support. There could be an issue with range propagation when applying constraints to the variables.
Sw expert at a manufacturing company with 5,001-10,000 employees
Real User
Top 10
Feb 8, 2024
There are two main areas of improvement. * False negatives and false positives. * The speed of the validation itself. Another area I see for improvement is scalability, particularly when dealing with large software systems. While Polyspace is effective for individual components and smaller applications, its performance can be impacted when analyzing entire systems all at once. There are limitations with handling large-scale applications.
Functional Safety Engineer at a manufacturing company with 5,001-10,000 employees
Real User
Nov 29, 2023
The run time analysis process must be improved. If we do not run with the main loop, it generates its own main and doesn’t allow developers to modify the execution sequences. The solution must provide more flexibility to the developers to manipulate the runtime analysis tools. The developer must be allowed to modify the main sequence. It will be very easy for them to test their use cases. Otherwise, Polyspace generates a random main file and executes all the functions randomly.
One of the main disadvantages is the time it takes to initiate the first run. Usually, there are a lot of errors initially, and you need to remove dependencies, such as compounded dependencies, to have an initial run. When we compared different tools, we found that the only drawback of Polyspace is the lead time required to have an output. There's something that can bypass the red errors. This is because you cannot base the policy solely on the presence of a red line or error. Sometimes, this mocks other errors from being reported.
Senior Engineer at a manufacturing company with 10,001+ employees
Real User
Apr 3, 2023
The speed is slow based on the bandwidth of the server we are using. The solution could be faster. 500KB of C-files will take 35 minutes to get results, and this could be sped up. Only .XML files are available for importing. I'd like the data to be taken from any format.
Specialist at a tech consulting company with 501-1,000 employees
Real User
Mar 31, 2023
There is room for improvement in automation related to the policies. We can work on scripting so that the tool automatically pops up, and with just a minimal amount of user input, we can repeat the execution. While manual processes are fine, automation is also required in today's industry, where time constraints exist in every delivery. Automation could be a challenge, but it is necessary for improvement. In the next release, I would like to have an automated testing environment integrated with Polyspace Code Prover, which can be activated with a single click.
Polyspace Code Prover is a sound static analysis tool that proves the absence of overflow, divide-by-zero, out-of-bounds array access, and certain other run-time errors in C and C++ source code. It produces results without requiring program execution, code instrumentation, or test cases. Polyspace Code Prover uses semantic analysis and abstract interpretation based on formal methods to verify software interprocedural, control, and data flow behavior. You can use it on handwritten code,...
Execution speed of the tests and generally the integration into AWS-driven CI work chains or workflows represent how it can be improved in my opinion. Performance issues plus license costs are two main driving factors. The CI environments that we use employ up to around 40,000 virtual CPUs per day in peak, running at the same time. We always have problems distributing licenses accordingly with other products. I can talk to the experts doing the integration, but as far as I know, I was involved with Polyspace Code Prover and we had a lot of difficulties integrating it into our Bazel-driven CI toolchain, plus integrating it on the AWS environments in Linux that we use. It was much more straightforward using Code Sonar there. The reason is the execution speed, integration with Azure and stuff, and pricing. The CI integration and maybe a better-suited license model for CI-driven execution are other areas I recommend improving. That's something we discussed with all of the software companies whose products we use, such as compilers. We have a lot of parallel builds, and each call to a license server is actually problematic in the long run.
I'm still trying to use constraints with range propagation, but I can't get it to work properly, and I haven't found any documentation. It require support. There could be an issue with range propagation when applying constraints to the variables.
There are two main areas of improvement. * False negatives and false positives. * The speed of the validation itself. Another area I see for improvement is scalability, particularly when dealing with large software systems. While Polyspace is effective for individual components and smaller applications, its performance can be impacted when analyzing entire systems all at once. There are limitations with handling large-scale applications.
The run time analysis process must be improved. If we do not run with the main loop, it generates its own main and doesn’t allow developers to modify the execution sequences. The solution must provide more flexibility to the developers to manipulate the runtime analysis tools. The developer must be allowed to modify the main sequence. It will be very easy for them to test their use cases. Otherwise, Polyspace generates a random main file and executes all the functions randomly.
One of the main disadvantages is the time it takes to initiate the first run. Usually, there are a lot of errors initially, and you need to remove dependencies, such as compounded dependencies, to have an initial run. When we compared different tools, we found that the only drawback of Polyspace is the lead time required to have an output. There's something that can bypass the red errors. This is because you cannot base the policy solely on the presence of a red line or error. Sometimes, this mocks other errors from being reported.
The speed is slow based on the bandwidth of the server we are using. The solution could be faster. 500KB of C-files will take 35 minutes to get results, and this could be sped up. Only .XML files are available for importing. I'd like the data to be taken from any format.
There is room for improvement in automation related to the policies. We can work on scripting so that the tool automatically pops up, and with just a minimal amount of user input, we can repeat the execution. While manual processes are fine, automation is also required in today's industry, where time constraints exist in every delivery. Automation could be a challenge, but it is necessary for improvement. In the next release, I would like to have an automated testing environment integrated with Polyspace Code Prover, which can be activated with a single click.