File: objdump_fi_ri.ll

package info (click to toggle)
llvm-toolchain-15 1%3A15.0.6-4
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 1,554,644 kB
  • sloc: cpp: 5,922,452; ansic: 1,012,136; asm: 674,362; python: 191,568; objc: 73,855; f90: 42,327; lisp: 31,913; pascal: 11,973; javascript: 10,144; sh: 9,421; perl: 7,447; ml: 5,527; awk: 3,523; makefile: 2,520; xml: 885; cs: 573; fortran: 567
file content (28 lines) | stat: -rw-r--r-- 1,303 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
; RUN: llc -march=bpfel -filetype=obj -o - %s \
; RUN:     | llvm-objdump --arch=bpfel --section=foo -d - \
; RUN:     | FileCheck %s

; This test was added because "isPseudo" flag was missing in FI_ri
; instruction definition and certain byte sequence caused an assertion
; in llvm-objdump tool.

; The value "G" is byte by byte little endian representation of the FI_ri instruction,
; as declared in the BPFInstrInfo.td.
; The first byte encodes an opcode: BPF_IMM(0x00) | BPF_DW(0x18) | BPF_LD(0x00)
; The second byte encodes source and destination registers: 2 and 0 respectively.
; The rest of the bytes are zeroes to comply with the specification.
; An additional 8 bytes follow the instruction as an immediate 64 bit argument,
; (because of the BPF_IMM flag).

; This is a pseudo instruction, meaning that it's not possible to
; write it in assembly directly. Thus it is coded as a byte array.

; Note the "bpfel" flags in the RUN command.

@G = constant [16 x i8]
              [i8 u0x18, i8 u0x20, i8 u0x00, i8 u0x00, i8 u0x00, i8 u0x00, i8 u0x00, i8 u0x00,
               i8 u0x00, i8 u0x00, i8 u0x00, i8 u0x00, i8 u0x00, i8 u0x00, i8 u0x00, i8 u0x00],
              section "foo", align 8

; CHECK-LABEL: G
; CHECK:       0: 18 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ld_pseudo r0, 2, 0