[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug ld/31177] New: AVR: Use __TEXT_REGION_ORIGIN__ as start for MEMORY
From: |
gjl at gcc dot gnu.org |
Subject: |
[Bug ld/31177] New: AVR: Use __TEXT_REGION_ORIGIN__ as start for MEMORY region text |
Date: |
Sun, 17 Dec 2023 18:06:11 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=31177
Bug ID: 31177
Summary: AVR: Use __TEXT_REGION_ORIGIN__ as start for MEMORY
region text
Product: binutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: ld
Assignee: unassigned at sourceware dot org
Reporter: gjl at gcc dot gnu.org
Target Milestone: ---
The start of MEMORY region text currently starts hard-coded at 0.
The linker can produce more exact diagnostics when it knows the exact
placements of the memory regions.
For some old devices, program memory starts at 0x8000, so allow to specify
program memory start at __TEXT_REGION_ORIGIN__ similar to how the data region
is described.
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug ld/31177] New: AVR: Use __TEXT_REGION_ORIGIN__ as start for MEMORY region text,
gjl at gcc dot gnu.org <=
- [Bug ld/31177] AVR: Use __TEXT_REGION_ORIGIN__ as start for MEMORY region text, gjl at gcc dot gnu.org, 2023/12/17
- [Bug ld/31177] AVR: Use __TEXT_REGION_ORIGIN__ as start for MEMORY region text, gjl at gcc dot gnu.org, 2023/12/17
- [Bug ld/31177] AVR: Use __TEXT_REGION_ORIGIN__ as start for MEMORY region text, gjl at gcc dot gnu.org, 2023/12/17
- [Bug ld/31177] AVR: Use __TEXT_REGION_ORIGIN__ as start for MEMORY region text, cvs-commit at gcc dot gnu.org, 2023/12/18
- [Bug ld/31177] AVR: Use __TEXT_REGION_ORIGIN__ as start for MEMORY region text, gjl at gcc dot gnu.org, 2023/12/18