Kaynağa Gözat

remove hackery for .debug_gdb_scripts section

This is no longer necessary now that we can configure the target to
exclude the .debug_gdb_scripts section.
See: https://github.com/rust-lang/rust/pull/53139
Dan Callaghan 6 yıl önce
ebeveyn
işleme
24290f1fd5
1 değiştirilmiş dosya ile 0 ekleme ve 16 silme
  1. 0 16
      riscv-rt/link.x

+ 0 - 16
riscv-rt/link.x

@@ -73,22 +73,6 @@ SECTIONS
     KEEP(*(.got .got.*));
     _egot = .;
   } > RAM AT > FLASH /* LLD fails on AT > FLASH */
-
-
-  /* Due to an unfortunate combination of legacy concerns,
-     toolchain drawbacks, and insufficient attention to detail,
-     rustc has no choice but to mark .debug_gdb_scripts as allocatable.
-     We really do not want to upload it to our target, so we
-     remove the allocatable bit. Unfortunately, it appears
-     that the only way to do this in a linker script is
-     the extremely obscure "INFO" output section type specifier. */
-  /* a rustc hack will force the program to read the first byte of this section,
-     so we'll set the (fake) start address of this section to something we're
-     sure can be read at runtime: the start of the .text section */
-  /* LLD fails to parse _stext (INFO) */
-  .debug_gdb_scripts _stext (INFO) : {
-    KEEP(*(.debug_gdb_scripts))
-  }
 }
 
 /* Do not exceed this mark in the error messages below                | */