[PATCH v2 0/5] Minor improvements to the bpf backend

Richard Henderson via llvm-commits llvm-commits at lists.llvm.org
Thu Jun 23 15:52:19 PDT 2016


Using EM_NONE for the bpf backend e_machine value is less than optimal.
With a unique value we can interact with other tools, e.g. objdump for
disassembly.

As a bonus, I noticed a few missing patterns that are useful to implement.

Changes v1-v2:
  * Official EM_BPF value,
  * Formatting nits corrected.


r~


Richard Henderson (5):
  BPF: Use a provisional ELF e_machine value
  BPF: Rearrange instruction classes
  BPF: Add NEG operation
  BPF: Add 32-bit move patterns
  BPF: Add 32-bit and pattern

 include/llvm/Object/ELFObjectFile.h                |   5 +
 include/llvm/Support/ELF.h                         |   7 +
 include/llvm/Support/ELFRelocs/BPF.def             |   9 +
 lib/Object/ELF.cpp                                 |   6 +
 lib/ObjectYAML/ELFYAML.cpp                         |   4 +
 lib/Target/BPF/BPFInstrFormats.td                  |  39 +-
 lib/Target/BPF/BPFInstrInfo.td                     | 598 +++++++++------------
 lib/Target/BPF/MCTargetDesc/BPFELFObjectWriter.cpp |   7 +-
 tools/llvm-objdump/llvm-objdump.cpp                |   1 +
 tools/llvm-readobj/ELFDumper.cpp                   |   1 +
 10 files changed, 340 insertions(+), 337 deletions(-)
 create mode 100644 include/llvm/Support/ELFRelocs/BPF.def

-- 
2.5.5



More information about the llvm-commits mailing list