• Show log

    Commit

  • Hash : cf888486
    Author : DRC
    Date : 2016-02-02T23:17:06

    Use consistent formatting in ARM NEON SIMD code
    
    There aren't really any best practices to follow here.  I tried as best
    as I could to adopt a standard that would ease any future maintenance
    burdens.  The basic tenets of that standard are:
    
    * Assembly instructions always start on Column 5, and operands always
      start on Column 21, except:
      - The instruction and operand can be indented (usually by 2 spaces)
        to indicate a separate instruction stream.
      - If the instruction is within an enclosing .if block in a macro,
        it should always be indented relative to the .if block.
    * Comments are placed with an eye toward readability.  There are always
      at least 2 spaces between the end of a line of code and the associated
      in-line comment.  Where it made sense, I tried to line up the comments
      in blocks, and some were shifted right to avoid overlap with
      neighboring instruction lines.  Not an exact science.
    * Assembler directives and macros use 2-space indenting rules.  .if
      blocks are indented relative to the macro, and code within the .if
      blocks is indented relative to the .if directive.
    * No extraneous spaces between operands.  Lining up the operands
      vertically did not really improve readability-- personally, I think it
      made it worse, since my eye would tend to lose its place in the
      uniform columns of characters.  Also, code with a lot of vertical
      alignment is really hard to maintain, since changing one line could
      necessitate changing a bunch of other lines to avoid spoiling the
      alignment.
    * No extraneous spaces in #defines or other directives.  In general, the
      only extraneous spaces (other than indenting spaces) are between:
      - Instructions and operands
      - Operands and in-line comments
    This standard should be more or less in keeping with other formatting
    standards used within the project.
    

  • Properties

  • Git HTTP https://git.kmx.io/kc3-lang/libjpeg-turbo.git
    Git SSH git@git.kmx.io:kc3-lang/libjpeg-turbo.git
    Public access ? public
    Description

    Fork of libjpeg with SIMD

    Users
    thodg_m kc3_lang_org thodg_w www_kmx_io thodg_l thodg
    Tags