diff --git a/riscv-elf.adoc b/riscv-elf.adoc
index edcd1e0..701c1a1 100644
--- a/riscv-elf.adoc
+++ b/riscv-elf.adoc
@@ -548,7 +548,9 @@ Description:: Additional information about the relocation
                                             <| S - P
 .2+| 65      .2+| TLSDESC_CALL      .2+| Static  |                   .2+| Annotate call to TLS descriptor resolver function, `%tlsdesc_call(address of %tlsdesc_hi)`, for relaxation purposes only
                                             <|
-.2+| 66-190  .2+| *Reserved*                          .2+| -       |                   .2+| Reserved for future standard use
+.2+| 66      .2+| LPAD              .2+| Static  |                   .2+| Annotates the landing pad instruction inserted at the beginning of the function. The addend indicates the label value of the landing pad, and the symbol value is the address of the mapping symbol for the function signature, which will have the same address as the function.
+                                            <|
+.2+| 67-190  .2+| *Reserved*                          .2+| -       |                   .2+| Reserved for future standard use
                                             <|
 .2+| 191     .2+| VENDOR        .2+| Static  |                   .2+| Paired with a vendor-specific relocation and must be placed immediately before it, indicates which vendor owns the relocation.
                                             <|
@@ -1582,6 +1584,7 @@ A number of symbols, named mapping symbols, describe the boundaries.
 | $x.<any>
 | $x<ISA>  .2+| Start of a sequence of instructions with <ISA> extension.
 | $x<ISA>.<any>
+| $s<function-signature-string> | Marker for the landing pad instruction. This should only be used with the function signature-based scheme and should be placed only at the beginning of the function.
 |===
 
 The mapping symbol should set the type to `STT_NOTYPE`, binding to `STB_LOCAL`,
@@ -2008,7 +2011,7 @@ NOTE: Tag_RISCV_x3_reg_usage is treated as 0 if it is not present.
 
   Relaxation::
   - The `auipc` instruction associated with `R_RISCV_GOT_HI20` can be
-  removed if the symbol is absolute.
+  removes if the symbol is absolute.
 
   - The instruction or instructions associated with `R_RISCV_PCREL_LO12_I`
   can be rewritten to either `c.li` or `addi` to materialize the symbol's
@@ -2317,6 +2320,96 @@ instructions. It is recommended to initialize `jvt` CSR immediately after
     csrw  jvt, a0
 ----
 
+==== Landing Pad Relaxation
+
+  Target Relocation::: R_RISCV_LPAD
+
+  Description:: This relaxation type allows the `lpad` instruction to be removed.
+  However, if `R_RISCV_RELAX` is not present, the `lpad` instruction can only be
+  replaced with a sequence of `nop` instructions of the same length as the
+  original instruction.
+
+  Description:: This relaxation type can relax lpad instruction into a none,
+  which removed the lpad instruction.
+  This relaxation type can be performed even without `R_RISCV_RELAX`,
+  but the linker should pad nop instruction to the same length of the original
+  instruction sequence.
+
+  Condition:: This relaxation can only be applied if the symbol is **NOT**
+  exported to the dynamic symbol table and is only referenced by `R_RISCV_CALL`
+  or `R_RISCV_CALL_PLT` relocations. If the symbol is exported or referenced by
+  other relocations, relaxation cannot be performed.
+
+  Relaxation::
+  - Lpad instruction associated with `R_RISCV_LPAD` can be removed.
+  - Lpad instruction associated with `R_RISCV_LPAD` can be replaced with nop
+    instruction if the relacation isn't paired with `R_RISCV_RELAX`.
+
+  Example::
++
+--
+Relaxation candidate:
+[,asm]
+----
+    lpad  0x123           # R_RISCV_LPAD, R_RISCV_RELAX
+----
+
+Relaxation result:
+[,asm]
+----
+    # No instruction
+----
+Can be relaxed into `nop` if no `R_RISCV_RELAX` is paired with `R_RISCV_LPAD`.
+[,asm]
+----
+    nop
+----
+--
+
+==== Landing Pad Scheme Relaxation
+
+  Target Relocation::: R_RISCV_LPAD
+
+  Description:: This relaxation type allows an `lpad` instruction to be relaxed
+  into `lpad 0`, which is a universal landing pad that ignores the label value
+  comparison. This relaxation is used when the label value is not computed
+  correctly.
+
+  Condition:: This relaxation can be performed without `R_RISCV_RELAX`, and
+  should not be enabled by default. The user must explicitly enable this
+  relaxation. Additionally, if this relaxation is applied, it must be applied
+  consistently to all `R_RISCV_LPAD` relocations in the entire binary.
+
+  Relaxation::
+  - Lpad instruction associated with `R_RISCV_LPAD` will be replaced with
+    `lpad 0`.
+  - The GNU property must be adjusted to reflect the use of this relaxation.
+  - The format of the PLT entries must also be adjusted accordingly.
+
+  Example::
++
+--
+Relaxation candidate:
+[,asm]
+----
+    lpad  0x123           # R_RISCV_LPAD
+----
+
+Relaxation result:
+[,asm]
+----
+    lpad 0
+----
+--
+
+NOTE: This relaxation is designed to be compatible with legacy programs that
+      may not declare the function signature correctly.
+
+NOTE: Dependent shared libraries will not undergo the corresponding
+transformation. Therefore, if this Landing Pad Scheme Relaxation is used in a
+dynamically linked environment, ensure that all dependent shared libraries are
+rebuilt with the corresponding version.
+
 [bibliography]
 == References