RIOT/makefiles/toolchain/gnu.inc.mk

CC         = $(PREFIX)gcc
CXX        = $(PREFIX)g++
CCAS      ?= $(CC)
ifeq ($(LTO),1)
  AR         = $(PREFIX)gcc-ar
  RANLIB     = $(PREFIX)gcc-ranlib
else
  AR         = $(PREFIX)ar
  RANLIB     = $(PREFIX)ranlib
endif
AS         = $(PREFIX)as
NM         = $(PREFIX)nm
LINK       = $(PREFIX)gcc
LINKXX     = $(PREFIX)g++
SIZE       = $(PREFIX)size
_OBJCOPY          := $(shell command -v $(PREFIX)objcopy || command -v gobjcopy || command -v objcopy)
OBJCOPY   ?= $(_OBJCOPY)
ifeq ($(OBJCOPY),)
  $(warning objcopy not found. Hex file will not be created.)
  OBJCOPY    = true
endif
# Default to the native (g)objdump, helps when using toolchain from docker
_OBJDUMP         := $(or $(shell command -v $(PREFIX)objdump || command -v gobjdump),objdump)
OBJDUMP   ?= $(_OBJDUMP)

GCC_VERSION := $(shell command -v $(CC) > /dev/null && $(CC) -dumpversion | cut -d . -f 1)

# -fmacro-prefix-map requires GCC 8
ifneq (8, $(firstword $(shell echo 8 $(GCC_VERSION) | tr ' ' '\n' | sort -n)))
  OPTIONAL_CFLAGS_BLACKLIST += -fmacro-prefix-map=$(RIOTBASE)/=
endif

# We use GDB for debugging
include $(RIOTMAKE)/tools/gdb.inc.mk

# Data address spaces starts at zero for all supported architectures. This fixes
# compilation at least on MSP430 and AVR.
# See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105523
ifneq (,$(filter $(GCC_VERSION),12 13))
  CFLAGS += --param=min-pagesize=0
endif
makefiles/toolchain: don't export all variables There are already exported globally in vars.inc.mk 2020-06-10 18:54:14 +02:00			`CC = $(PREFIX)gcc`
			`CXX = $(PREFIX)g++`
			`CCAS ?= $(CC)`
cpu/cortexm_common: Use gcc-ar when building with LTO gcc-ar is a wrapper supplied by gcc for properly handling thin LTO objects. 2015-07-10 11:57:43 +02:00			`ifeq ($(LTO),1)`
makefiles/toolchain: don't export all variables There are already exported globally in vars.inc.mk 2020-06-10 18:54:14 +02:00			`AR = $(PREFIX)gcc-ar`
			`RANLIB = $(PREFIX)gcc-ranlib`
cpu/cortexm_common: Use gcc-ar when building with LTO gcc-ar is a wrapper supplied by gcc for properly handling thin LTO objects. 2015-07-10 11:57:43 +02:00			`else`
makefiles/toolchain: don't export all variables There are already exported globally in vars.inc.mk 2020-06-10 18:54:14 +02:00			`AR = $(PREFIX)ar`
			`RANLIB = $(PREFIX)ranlib`
cpu/cortexm_common: Use gcc-ar when building with LTO gcc-ar is a wrapper supplied by gcc for properly handling thin LTO objects. 2015-07-10 11:57:43 +02:00			`endif`
makefiles/toolchain: don't export all variables There are already exported globally in vars.inc.mk 2020-06-10 18:54:14 +02:00			`AS = $(PREFIX)as`
			`NM = $(PREFIX)nm`
			`LINK = $(PREFIX)gcc`
			`LINKXX = $(PREFIX)g++`
			`SIZE = $(PREFIX)size`
makefiles/gnu.inc.mk: Use simple expansion for OBJCOPY and OBJDUMP 2020-02-04 15:21:24 +01:00			`_OBJCOPY := $(shell command -v $(PREFIX)objcopy \|\| command -v gobjcopy \|\| command -v objcopy)`
makefiles/toolchain: don't export all variables There are already exported globally in vars.inc.mk 2020-06-10 18:54:14 +02:00			`OBJCOPY ?= $(_OBJCOPY)`
make: use gobjcopy if objcopy is not available 2016-10-31 22:28:43 +01:00			`ifeq ($(OBJCOPY),)`
makefiles/toolchain: don't export all variables There are already exported globally in vars.inc.mk 2020-06-10 18:54:14 +02:00			`$(warning objcopy not found. Hex file will not be created.)`
			`OBJCOPY = true`
make: use gobjcopy if objcopy is not available 2016-10-31 22:28:43 +01:00			`endif`
makefiles/toolchain: fallback to 'objdump' When '$(PREFIX)objdump' is not present fallback to native '(g)objdump'. 'objdump' is used when flashing for some boards but the toolchain may not be installed when building in docker. This will allow using 'objdump' in 'cpu/kinetis/dist/check-fcfield.sh'. 2019-01-25 16:55:37 +01:00			`# Default to the native (g)objdump, helps when using toolchain from docker`
makefiles/gnu.inc.mk: Use simple expansion for OBJCOPY and OBJDUMP 2020-02-04 15:21:24 +01:00			`_OBJDUMP := $(or $(shell command -v $(PREFIX)objdump \|\| command -v gobjdump),objdump)`
makefiles/toolchain: don't export all variables There are already exported globally in vars.inc.mk 2020-06-10 18:54:14 +02:00			`OBJDUMP ?= $(_OBJDUMP)`
makefiles/gnu.inc.mk: set flags based on compiler version 2022-11-18 23:29:12 +01:00
toolchain/gnu.inc.mk: don't check version if CC is not installed With b30efeeb65 a warning was introduced when using `make term` without the proper toolchain installed (e.g. when using BUILD_IN_DOCKER, but `term` outside of the docker). This removes this warning 2023-01-13 11:44:06 +01:00			`GCC_VERSION := $(shell command -v $(CC) > /dev/null && $(CC) -dumpversion \| cut -d . -f 1)`
makefiles/gnu.inc.mk: set flags based on compiler version 2022-11-18 23:29:12 +01:00
			`# -fmacro-prefix-map requires GCC 8`
makefiles/gnu.inc.mk: fix "extraneous text after 'ifneq' directive" When trying to compile `examples/hello-world` on my 465 MHz Mendocino I got /home/benpicco/dev/RIOT/makefiles/toolchain/gnu.inc.mk:29: extraneous text after 'ifneq' directive Turns out the version of `make` on Archlinux32 is newer than that in Ubuntu 22.04, which somehow ignored the extra parenthesis. Turns out this (t)rusty old machine is still good for writing patches :D 2022-11-20 14:48:52 +01:00			`ifneq (8, $(firstword $(shell echo 8 $(GCC_VERSION) \| tr ' ' '\n' \| sort -n)))`
makefiles/gnu.inc.mk: set flags based on compiler version 2022-11-18 23:29:12 +01:00			`OPTIONAL_CFLAGS_BLACKLIST += -fmacro-prefix-map=$(RIOTBASE)/=`
			`endif`

makefiles: Split GDB settings from toolchain 2017-10-06 13:51:47 +02:00			`# We use GDB for debugging`
			`include $(RIOTMAKE)/tools/gdb.inc.mk`
makefiles/toolchain: Fix incorrect assumptions on address space layout GCC 12 gives out of bounds warnings when the resulting address is out of bounds of what GCC assumes to be the valid address space. It seems that by default the address 0x0 is not considered valid (which would be a NULL pointer and typically not mapped in a userspace behind an MMU scenario), but in fact is valid on bare metal hardware. At least on AVR and MSP430 this needs to be set. On many Cortex M MCUs 0x0 is also a valid address (e.g. often the flash is mapped there), but seemingly for them `--param=min-pagesize=0` is already the default. In any case, it won't hurt to set it explicit for them as well. 2023-04-21 08:57:30 +02:00
			`# Data address spaces starts at zero for all supported architectures. This fixes`
			`# compilation at least on MSP430 and AVR.`
			`# See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105523`
makefiles/toolchain/gnu.inc.mk: fix compilation The `--param=min-pagesize=0` needed since GCC 12 is still needed with GCC 13. This time at least the message is more meaningful: note: source object is likely at address zero This is something that is not expected in a userspace app, but with bare metal MCUs and often flash or memory mapped I/O starting from address zero, this warning prevents legitimate code from compiling. 2023-06-03 20:10:56 +02:00			`ifneq (,$(filter $(GCC_VERSION),12 13))`
makefiles/toolchain: Fix incorrect assumptions on address space layout GCC 12 gives out of bounds warnings when the resulting address is out of bounds of what GCC assumes to be the valid address space. It seems that by default the address 0x0 is not considered valid (which would be a NULL pointer and typically not mapped in a userspace behind an MMU scenario), but in fact is valid on bare metal hardware. At least on AVR and MSP430 this needs to be set. On many Cortex M MCUs 0x0 is also a valid address (e.g. often the flash is mapped there), but seemingly for them `--param=min-pagesize=0` is already the default. In any case, it won't hurt to set it explicit for them as well. 2023-04-21 08:57:30 +02:00			`CFLAGS += --param=min-pagesize=0`
			`endif`