u-boot.git/Makefile, branch v2021.07

Prepare v2021.07

2021-07-05T15:11:28+00:00

Signed-off-by: Tom Rini

Revert "TEST: USB_HOST not USB"

2021-06-30T17:10:02+00:00

This reverts commit 4e1903a645453deab5ec5dd1cf4f0061469b99c3.

This local commit was not intended to be pushed out.

Signed-off-by: Tom Rini

TEST: USB_HOST not USB

2021-06-30T15:38:52+00:00

Signed-off-by: Tom Rini

Prepare v2021.07-rc5

2021-06-28T19:38:55+00:00

Signed-off-by: Tom Rini

Makefile: Adjust indention of GENENV quiet output

2021-06-22T18:01:22+00:00

The column width for a command name is 8.

Signed-off-by: Jan Kiszka

Prepare v2021.07-rc4

2021-06-07T13:26:39+00:00

Signed-off-by: Tom Rini

Prepare v2021.07-rc3

2021-05-25T00:53:13+00:00

Signed-off-by: Tom Rini

build: link with --build-id=none

2021-05-24T18:21:30+00:00

Some toolchains are compiled so that they pass a --build-id=something
parameter to the linker implicitly.

This causes U-Boot LTO linking to fail with something like:
  ld: section .note.gnu.build-id LMA ... overlaps section .text LMA ...
because U-Boot's link scripts do not currently handle .note.gnu.build-id
section.

Fix this by explicitly disabling build-id.

Signed-off-by: Marek Behún 
Reviewed-by: Simon Glass

build: support building with Link Time Optimizations

2021-05-24T18:21:30+00:00

Add plumbing for building U-Boot with Link Time Optimizations.

When building with LTO, $(PLATFORM_LIBS) has to be in --whole-archive /
--no-whole-archive group, otherwise some functions declared in assembly
may not be resolved and linking may fail.

Note: clang may throw away linker list symbols it thinks are unused when
compiling with LTO. To force these symbols to be included, we refer to
them via the __ADDRESSABLE macro in a C file generated from compiled
built-in.o files before linking.

Signed-off-by: Marek Behún 
Reviewed-by: Simon Glass

build: use thin archives instead of incremental linking

2021-05-24T18:21:30+00:00

Currently we use incremental linking (ld -r) to link several object
files from one directory into one built-in.o object file containing the
linked code from that directory (and its subdirectories).

Linux has, some time ago, moved to thin archives instead.

Thin archives are archives (.a) that do not really contain the object
files, only references to them.

Using thin archives instead of incremental linking
- saves disk space
- apparently works better with dead code elimination
- makes things easier for LTO

The third point is the important one for us. With incremental linking
there are several options how to do LTO, and that would unnecessarily
complicate things.

We have to use the --whole-archive/--no-whole-archive linking option
instead of --start-group/--end-group, otherwise linking may fail because
of unresolved symbols, or the resulting binary will be unusable.

We also need to use the P flag for ar, otherwise final linking may fail.

Signed-off-by: Marek Behún 
Reviewed-by: Simon Glass