[HN Gopher] Optimizing your programs for Arm platforms
       ___________________________________________________________________
        
       Optimizing your programs for Arm platforms
        
       Author : Phyx
       Score  : 15 points
       Date   : 2024-04-26 12:10 UTC (10 hours ago)
        
 (HTM) web link (community.arm.com)
 (TXT) w3m dump (community.arm.com)
        
       | astrange wrote:
       | This isn't a good article. I would say that if you're trying to
       | rely on `restrict` and autovectorization you're doomed and should
       | write it yourself. Even if it works on one compiler version, it
       | won't work on all of them.
       | 
       | (It could possibly work in a language that isn't C and is
       | designed for it; Fortran or shader programs are easier to
       | autovectorize, and something like ISPC starts out "vectorized"
       | and gets "autoscalarized".)
       | 
       | This is why ffmpeg writes SIMD in assembly and is more successful
       | than all the people constantly replying "um actually you never
       | need to write anything in assembly" to them.
        
         | ColonelPhantom wrote:
         | Aren't shader programs more like ISPC (or OpenCL/CUDA), in that
         | the programming model is based around 'pretend each SIMD lane
         | is thread'?
        
       | rarepostinlurkr wrote:
       | It's good so much attention is being given to arm! Apple also
       | recently released more details on optimization
       | 
       | https://developer.apple.com/documentation/apple-silicon/cpu-...
        
         | electricshampo1 wrote:
         | Thanks for this link; did not realize that they did this.
        
       ___________________________________________________________________
       (page generated 2024-04-26 23:01 UTC)