Revert "[AVR] Explicitly set the address of the data section when invoking the linker"

This reverts commit ede6005e70.

Ayke suggests this value varies chip-by-chip, and thus it is not safe to
hardcode to 0x800100.

Proper logic for this linker parameter will have to be wired up in a
follow up patch.
This commit is contained in:
Dylan McKay 2020-06-23 22:21:22 +12:00
parent d668d8b619
commit 15b9dc46c6
1 changed files with 0 additions and 7 deletions

View File

@ -118,13 +118,6 @@ void AVR::Linker::ConstructJob(Compilation &C, const JobAction &JA,
Args.AddAllArgs(CmdArgs, options::OPT_L);
getToolChain().AddFilePathLibArgs(Args, CmdArgs);
// "Not [sic] that addr must be offset by adding 0x800000 the to
// real SRAM address so that the linker knows that the address
// is in the SRAM memory space."
//
// - https://www.nongnu.org/avr-libc/user-manual/mem_sections.html
CmdArgs.push_back("-Tdata=0x800100");
// If the family name is known, we can link with the device-specific libgcc.
// Without it, libgcc will simply not be linked. This matches avr-gcc
// behavior.