This PR fixed all warnings for standard application.
Anyway, if a Flash operation (write) is performedclosed to the code segment warning can be raised.
Main example is when the EEPROM emulation is used as it uses last flash page, mainly for mcu with small flash size.

I've reproduced easily with a Blink example on a STM32L4 target by adding:

  FLASH_EraseInitTypeDef EraseInitStruct;  uint32_t pageError = 0;  HAL_FLASHEx_Erase(&EraseInitStruct, &pageError);  HAL_FLASH_Program(FLASH_TYPEPROGRAM_DOUBLEWORD, 0x0800F000, 10);

To go further, warning is reached due to the usage of at least one RAM function:
#define __RAM_FUNC __attribute__((section(".RamFunc")))

Example with HAL FLASH API:

So, I kept the warning disabled, but new linker script should use theREADONLY attribute to prevent warning.