extended instructions(NEON) get stuck

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • arvin
    Junior Member
    • Aug 2021
    • 13

    #16
    popped up "Illegal instruction" while executing ./simd_arm32_10.1.1004.2, not sure if there's anything wrong?
    Attached Files
    Last edited by arvin; Sep-03-2021, 08:59 AM.

    Comment

    • arvin
      Junior Member
      • Aug 2021
      • 13

      #17
      please find attached for simd_debug.log file. thanks.
      Attached Files

      Comment

      • David.K (Passmark)
        Junior Member
        • Oct 2020
        • 13

        #18
        Thanks for that, I think we've tracked down the problem.

        Looks like a problem with ARMv7 CPU's with neon extensions but missing the CPU extended instruction vfpv4. It seems vfpv4 is in most v7 CPUs but not all. It was made standard in ARMv8.

        Could you try this PerformanceTest build (pt_linux_arm32_debug10.1.1005) and let us know if it works.
        Last edited by David.K (Passmark); Sep-15-2021, 05:22 AM.

        Comment

        • arvin
          Junior Member
          • Aug 2021
          • 13

          #19
          Thanks for new version trying, looks CPU Mark still Incomplete as attached.
          Attached Files

          Comment

          • David.K (Passmark)
            Junior Member
            • Oct 2020
            • 13

            #20
            Thought that would have fixed the problem.

            Could you upload the "debug.log" file from that build?

            Comment

            • arvin
              Junior Member
              • Aug 2021
              • 13

              #21
              should the right one from time point of view, thanks.
              Attached Files

              Comment

              • David.K (Passmark)
                Junior Member
                • Oct 2020
                • 13

                #22
                Could you send us the name of the device you're using and where you purchased it?

                We might look into buying one ourselves to get to the bottom of this issue.

                Comment

                Working...