On 12/19/24 11:36 PM, Georg-Johann Lay wrote:
This is a ping for
https://gcc.gnu.org/pipermail/gcc-patches/2024-December/671216.html
I'd prefer this to wait for gcc-16 as we're well into stage3. While
using a hook makes it fairly safe, I think everyone is quite busy with
stage3 activities.
This is a ping for
https://gcc.gnu.org/pipermail/gcc-patches/2024-December/671216.html
Johann
This patch adds a new target hook that allows to chose
a non-generic named address-space for compiler generated
lookup tables.
The purpose is that there are cases (on avr namely) where
the generic ad
For the avr.cc part, the __flashx named address space has been approved,
which means that the natural choice in the target hook would be
ADDR_SPACE_FLASHX instead of ADDR_SPACE_MEMX:
+/* Implement `TARGET_ADDR_SPACE_FOR_ARTIFICIAL_RODATA'. */
+
+static addr_space_t
+avr_addr_space_for_artificia
This patch adds a new target hook that allows to chose
a non-generic named address-space for compiler generated
lookup tables.
The purpose is that there are cases (on avr namely) where
the generic address space is sub-optimal because it must
put .rodata in RAM. With this hook it is possible to
c
