When to use earlyclobber constraint in extended GCC inline assembly?

by

By default, the compiler assumes all inputs will be consumed before any output registers are written to, so that it’s allowed to use the same registers for both. This leads to better code when possible, but if the assumption is wrong, things will fail catastrophically. The “early clobber” marker is a way to tell the compiler that this output will be written before all the input has been consumed, so it cannot share a register with any input.

GNU C inline asm syntax was designed to wrap a single instruction as efficiently as possible. You can put multiple instructions in an asm template, but the defaults (assuming that all inputs are read before any outputs are written) are designed around wrapping a single instruction.

It’s the same constraint syntax as GCC uses in its machine-description files that teach the compiler what instructions are available in an ISA.

More Related Contents:

  1. Assembly code fsqrt and fmul instructions
  2. How can I indicate that the memory *pointed* to by an inline ASM argument may be used?
  3. What is the difference between ‘asm’, ‘__asm’ and ‘__asm__’?
  4. Can I use Intel syntax of x86 assembly with GCC?
  5. Looping over arrays with inline assembly
  6. How to access C variable for inline assembly manipulation?
  7. Reading a register value into a C variable [duplicate]
  8. Why we need Clobbered registers list in Inline Assembly?
  9. How to tell GCC to generate 16-bit code for real mode
  10. Using condition flags as GNU C inline asm outputs
  11. Using GCC to produce readable assembly?
  12. Adding leading underscores to assembly symbols with GCC on Win32?
  13. How does GCC implement variable-length arrays?
  14. What does it mean to align the stack?
  15. Labels in GCC inline assembly
  16. Efficient integer compare function
  17. Why is the value of EDX overwritten when making call to printf?
  18. Alloca implementation
  19. How can I multiply 64 bit operands and get 128 bit result portably?
  20. In GNU C inline asm, what are the size-override modifiers for xmm/ymm/zmm for a single operand?
  21. x86_64 : is stack frame pointer almost useless?
  22. execute binary machine code from C
  23. calling assembly function from c
  24. The difference between asm, asm volatile and clobbering memory
  25. Why do compilers insist on using a callee-saved register here?
  26. Compiler changes printf to puts
  27. Why is gcc allowed to speculatively load from a struct?
  28. How to get the size of a C function from inside a C program or with inline assembly?
  29. What is the effect of second argument in _builtin_prefetch()?
  30. How do I compile the asm generated by GCC?

Leave a Comment