Recherche avancée

Sur d’autres sites (11147)

• ARM inline asm secrets

  6 juillet 2010, par Mans — ARM, Compilers

  Although I generally recommend against using GCC inline assembly, preferring instead pure assembly code in separate files, there are occasions where inline is the appropriate solution. Should one, at a time like this, turn to the GCC documentation for guidance, one must be prepared for a degree of disappointment. As it happens, much of the inline asm syntax is left entirely undocumented. This article attempts to fill in some of the blanks for the ARM target.
  

  Constraints

  Each operand of an inline asm block is described by a constraint string encoding the valid representations of the operand in the generated assembly. For example the “r” code denotes a general-purpose register. In addition to the standard constraints, ARM allows a number of special codes, only some of which are documented. The full list, including a brief description, is available in the constraints.md file in the GCC source tree. The following table is an extract from this file consisting of the codes which are meaningful in an inline asm block (a few are only useful in the machine description itself).

  f	Legacy FPA registers f0-f7.
  t	The VFP registers s0-s31.
  v	The Cirrus Maverick co-processor registers.
  w	The VFP registers d0-d15, or d0-d31 for VFPv3.
  x	The VFP registers d0-d7.
  y	The Intel iWMMX co-processor registers.
  z	The Intel iWMMX GR registers.
  l	In Thumb state the core registers r0-r7.
  h	In Thumb state the core registers r8-r15.
  j	A constant suitable for a MOVW instruction. (ARM/Thumb-2)
  b	Thumb only. The union of the low registers and the stack register.
  I	In ARM/Thumb-2 state a constant that can be used as an immediate value in a Data Processing instruction. In Thumb-1 state a constant in the range 0 to 255.
  J	In ARM/Thumb-2 state a constant in the range -4095 to 4095. In Thumb-1 state a constant in the range -255 to -1.
  K	In ARM/Thumb-2 state a constant that satisfies the I constraint if inverted. In Thumb-1 state a constant that satisfies the I constraint multiplied by any power of 2.
  L	In ARM/Thumb-2 state a constant that satisfies the I constraint if negated. In Thumb-1 state a constant in the range -7 to 7.
  M	In Thumb-1 state a constant that is a multiple of 4 in the range 0 to 1020.
  N	Thumb-1 state a constant in the range 0 to 31.
  O	In Thumb-1 state a constant that is a multiple of 4 in the range -508 to 508.
  Pa	In Thumb-1 state a constant in the range -510 to +510
  Pb	In Thumb-1 state a constant in the range -262 to +262
  Ps	In Thumb-2 state a constant in the range -255 to +255
  Pt	In Thumb-2 state a constant in the range -7 to +7
  G	In ARM/Thumb-2 state a valid FPA immediate constant.
  H	In ARM/Thumb-2 state a valid FPA immediate constant when negated.
  Da	In ARM/Thumb-2 state a const_int, const_double or const_vector that can be generated with two Data Processing insns.
  Db	In ARM/Thumb-2 state a const_int, const_double or const_vector that can be generated with three Data Processing insns.
  Dc	In ARM/Thumb-2 state a const_int, const_double or const_vector that can be generated with four Data Processing insns. This pattern is disabled if optimizing for space or when we have load-delay slots to fill.
  Dn	In ARM/Thumb-2 state a const_vector which can be loaded with a Neon vmov immediate instruction.
  Dl	In ARM/Thumb-2 state a const_vector which can be used with a Neon vorr or vbic instruction.
  DL	In ARM/Thumb-2 state a const_vector which can be used with a Neon vorn or vand instruction.
  Dv	In ARM/Thumb-2 state a const_double which can be used with a VFP fconsts instruction.
  Dy	In ARM/Thumb-2 state a const_double which can be used with a VFP fconstd instruction.
  Ut	In ARM/Thumb-2 state an address valid for loading/storing opaque structure types wider than TImode.
  Uv	In ARM/Thumb-2 state a valid VFP load/store address.
  Uy	In ARM/Thumb-2 state a valid iWMMX load/store address.
  Un	In ARM/Thumb-2 state a valid address for Neon doubleword vector load/store instructions.
  Um	In ARM/Thumb-2 state a valid address for Neon element and structure load/store instructions.
  Us	In ARM/Thumb-2 state a valid address for non-offset loads/stores of quad-word values in four ARM registers.
  Uq	In ARM state an address valid in ldrsb instructions.
  Q	In ARM/Thumb-2 state an address that is a single base register.

  Operand codes

  Within the text of an inline asm block, operands are referenced as %0, %1 etc. Register operands are printed as rN, memory operands as [rN, #offset], and so forth. In some situations, for example with operands occupying multiple registers, more detailed control of the output may be required, and once again, an undocumented feature comes to our rescue.

  Special code letters inserted between the % and the operand number alter the output from the default for each type of operand. The table below lists the more useful ones.

  c	An integer or symbol address without a preceding # sign
  B	Bitwise inverse of integer or symbol without a preceding #
  L	The low 16 bits of an immediate constant
  m	The base register of a memory operand
  M	A register range suitable for LDM/STM
  H	The highest-numbered register of a pair
  Q	The least significant register of a pair
  R	The most significant register of a pair
  P	A double-precision VFP register
  p	The high single-precision register of a VFP double-precision register
  q	A NEON quad register
  e	The low doubleword register of a NEON quad register
  f	The high doubleword register of a NEON quad register
  h	A range of VFP/NEON registers suitable for VLD1/VST1
  A	A memory operand for a VLD1/VST1 instruction
  y	S register as indexed D register, e.g. s5 becomes d2[1]

• "Cannot find ffmpeg" error when using 'audioconcat'

  2 janvier 2020, par Mosukoshide

  I would like to concatenate three ’.oga’ sound files using audioconcat, however whenever I try to do so, I am met with this error :

  Error: Error: Cannot find ffmpeg
  
      at /root/user/node_modules/fluent-ffmpeg/lib/processor.js:136:22
  
      at /root/user/node_modules/fluent-ffmpeg/lib/capabilities.js:123:9
  
      at /root/user/node_modules/fluent-ffmpeg/lib/capabilities.js:116:11
  
      at /root/user/node_modules/fluent-ffmpeg/lib/utils.js:223:16
  
      at F (/root/user/node_modules/which/which.js:68:16)
  
      at E (/root/user/node_modules/which/which.js:80:29)
  
      at /root/user/node_modules/which/which.js:89:16
  
      at /root/user/node_modules/isexe/index.js:42:5
  
      at /root/user/node_modules/isexe/mode.js:8:5
  
      at FSReqWrap.oncomplete (fs.js:152:21)
  
  ffmpeg stderr: undefined

  I have already installed ffmpeg with the flags that were listed on the audioconcat npm page like this :

  npm i ffmpeg --enable-libass --enable-libmp3lame

  And the code I am trying to run looks like this :

                  audioconcat(audioFiles)
  
                  .concat(`main.oga`)
  
                  .on('start', function (command) {
  
                    console.log('ffmpeg process started:', command)
  
                  })
  
                  .on('error', function (err, stdout, stderr) {
  
                    console.error('Error:', err)
  
                    console.error('ffmpeg stderr:', stderr)
  
                  })
  
                  .on('end', function (output) {
  
                    console.error('Audio created in:', output)
  
                  })

  I’m not sure how to fix this problem...

• Recursively running ffmpeg concat script in bash across multiple folders

  15 août 2022, par Sam Feldman

  I wrote a bash script that concatenates all video files in a folder using ffmpeg. I would like to be able to run this script recursively on multiple folders. My problem has been that I am unable to change into the directory of every new folder to run the script. This is required for my script to work. Does anyone know what I could accomplish this ?

  


      #!/bin/bash

for f in *; do echo "file '$f'" >> files.txt; done
for f in *; do echo "'$f'" >> filesdelete.txt; done
ffmpeg -f concat -safe 0 -i files.txt -c copy "${PWD##*/}".MP4
xargs -I{} rm -r "{}" < filesdelete.txt
rm files.txt
rm filesdelete.txt


  


  I start with the file structure below. The script runs in each subdirectory (dir1, dir2, dir3) and combines the files in each subdirectory into one video. For the script to run, it needs to cd into each directory.

  


  root
├── dir1
│   ├── video1.mp4
│   ├── video2.mp4
│   └── video3.mp4
├── dir2
│   ├── video1.mp4
│   └── video2.mp4
└── dir3
    ├── video1.mp4
    └── video2.mp4


  


  The end result should look like the structure below.

  


  root
├── dir1
│   └── concat.mp4
├── dir2
│   └── concat.mp4
└── dir3
    └── concat.mp4