diff options
author | Xi Ruoyao <xry111@xry111.site> | 2024-07-11 19:43:48 +0800 |
---|---|---|
committer | Lulu Cheng <chenglulu@loongson.cn> | 2024-10-08 10:41:25 +0800 |
commit | 0ee028f556401846d27edf0ff67647a1a7a26b6c (patch) | |
tree | 40fb835273cb08e025a036ef29bd4dd464e808f0 /gcc | |
parent | c01e3aaae79ecd439ad35063db3dee9775f3aefa (diff) | |
download | gcc-0ee028f556401846d27edf0ff67647a1a7a26b6c.zip gcc-0ee028f556401846d27edf0ff67647a1a7a26b6c.tar.gz gcc-0ee028f556401846d27edf0ff67647a1a7a26b6c.tar.bz2 |
LoongArch: Add support to annotate tablejump
This is per the request from the kernel developers. For generating the
ORC unwind info, the objtool program needs to analysis the control flow
of a .o file. If a jump table is used, objtool has to correlate the
jump instruction with the table.
On x86 (where objtool was initially developed) it's simple: a relocation
entry natrually correlates them because one single instruction is used
for table-based jump. But on an RISC machine objtool would have to
reconstruct the data flow if it must find out the correlation on its
own.
So, emit an additional section to store the correlation info as pairs of
addresses, each pair contains the address of a jump instruction (jr) and
the address of the jump table. This is very trivial to implement in
GCC.
gcc/ChangeLog:
* config/loongarch/genopts/loongarch.opt.in
(mannotate-tablejump): New option.
* config/loongarch/loongarch.opt: Regenerate.
* config/loongarch/loongarch.md (tablejump<mode>): Emit
additional correlation info between the jump instruction and the
jump table, if -mannotate-tablejump.
* doc/invoke.texi: Document -mannotate-tablejump.
gcc/testsuite/ChangeLog:
* gcc.target/loongarch/jump-table-annotate.c: New test.
Suggested-by: Tiezhu Yang <yangtiezhu@loongson.cn>
Diffstat (limited to 'gcc')
-rw-r--r-- | gcc/config/loongarch/genopts/loongarch.opt.in | 4 | ||||
-rw-r--r-- | gcc/config/loongarch/loongarch.md | 12 | ||||
-rw-r--r-- | gcc/config/loongarch/loongarch.opt | 4 | ||||
-rw-r--r-- | gcc/doc/invoke.texi | 13 | ||||
-rw-r--r-- | gcc/testsuite/gcc.target/loongarch/jump-table-annotate.c | 15 |
5 files changed, 46 insertions, 2 deletions
diff --git a/gcc/config/loongarch/genopts/loongarch.opt.in b/gcc/config/loongarch/genopts/loongarch.opt.in index d00950c..d5bbf01 100644 --- a/gcc/config/loongarch/genopts/loongarch.opt.in +++ b/gcc/config/loongarch/genopts/loongarch.opt.in @@ -301,3 +301,7 @@ default value is 4. ; CPUCFG independently, so we use bit flags to specify them. TargetVariable HOST_WIDE_INT la_isa_evolution = 0 + +mannotate-tablejump +Target Mask(ANNOTATE_TABLEJUMP) Save +Annotate table jump instruction (jr {reg}) to correlate it with the jump table. diff --git a/gcc/config/loongarch/loongarch.md b/gcc/config/loongarch/loongarch.md index f70ca85..bd08250 100644 --- a/gcc/config/loongarch/loongarch.md +++ b/gcc/config/loongarch/loongarch.md @@ -3496,12 +3496,22 @@ DONE; }) +(define_mode_attr mode_size [(DI "8") (SI "4")]) + (define_insn "@tablejump<mode>" [(set (pc) (match_operand:P 0 "register_operand" "e")) (use (label_ref (match_operand 1 "" "")))] "" - "jr\t%0" + { + return TARGET_ANNOTATE_TABLEJUMP + ? "1:jr\t%0\n\t" + ".pushsection\t.discard.tablejump_annotate\n\t" + "\t.<mode_size>byte\t1b\n\t" + "\t.<mode_size>byte\t%1\n\t" + ".popsection" + : "jr\t%0"; + } [(set_attr "type" "jump") (set_attr "mode" "none")]) diff --git a/gcc/config/loongarch/loongarch.opt b/gcc/config/loongarch/loongarch.opt index 91cb523..6a396b5 100644 --- a/gcc/config/loongarch/loongarch.opt +++ b/gcc/config/loongarch/loongarch.opt @@ -310,6 +310,10 @@ default value is 4. TargetVariable HOST_WIDE_INT la_isa_evolution = 0 +mannotate-tablejump +Target Mask(ANNOTATE_TABLEJUMP) Save +Annotate table jump instruction (jr {reg}) to correlate it with the jump table + mfrecipe Target Mask(ISA_FRECIPE) Var(la_isa_evolution) Support frecipe.{s/d} and frsqrte.{s/d} instructions. diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 987b636..b2f16b4 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -1071,7 +1071,7 @@ Objective-C and Objective-C++ Dialects}. -mcmodel=@var{code-model} -mrelax -mpass-mrelax-to-as -mrecip -mrecip=@var{opt} -mfrecipe -mno-frecipe -mdiv32 -mno-div32 -mlam-bh -mno-lam-bh -mlamcas -mno-lamcas -mld-seq-sa -mno-ld-seq-sa --mtls-dialect=@var{opt}} +-mtls-dialect=@var{opt} -mannotate-tablejump -mno-annotate-tablejump} @emph{M32R/D Options} @gccoptlist{-m32r2 -m32rx -m32r @@ -27512,6 +27512,17 @@ Whether a load-load barrier (@code{dbar 0x700}) is needed. When build with This option controls which tls dialect may be used for general dynamic and local dynamic TLS models. +@opindex mannotate-tablejump +@opindex mno-annotate-tablejump +@item -mannotate-tablejump +@itemx -mno-annotate-tablejump +Create an annotation section @code{.discard.tablejump_annotate} to +correlate the @code{jirl} instruction and the jump table when a jump +table is used to optimize the @code{switch} statement. Some external +tools, for example @file{objtool} of the Linux kernel building system, +need the annotation to analysis the control flow. The default is +@option{-mno-annotate-tablejump}. + @table @samp @item trad Use traditional TLS. This is the default. diff --git a/gcc/testsuite/gcc.target/loongarch/jump-table-annotate.c b/gcc/testsuite/gcc.target/loongarch/jump-table-annotate.c new file mode 100644 index 0000000..9d58e60 --- /dev/null +++ b/gcc/testsuite/gcc.target/loongarch/jump-table-annotate.c @@ -0,0 +1,15 @@ +/* { dg-do compile } */ +/* { dg-additional-options "-mannotate-tablejump" } */ + +extern void asdf(int); +void foo(int x) { + switch (x) { + case 0: asdf(10); break; + case 1: asdf(11); break; + case 2: asdf(12); break; + case 3: asdf(13); break; + case 4: asdf(14); break; + } +} + +/* { dg-final { scan-assembler "\\.discard\\.tablejump_annotate" } } */ |