Comment # 18 on bug 936463 from Stanislav Brabec

Thank for the notes.

avr-libc and avr-gcc is now in CrossToolchain:avr project. As they are now in
/opt/cross prefix, they cannot be accepted to Factory.

My goal is:

- Move both from /opt/cross to /usr, so they could be candidates for Factory.

- Compile avr-libc with gcc5.

- Make avr-gcc completely empty, just keep small wrappers with convenient
names, preconfigured to make them compatible with Arduino and other tools (i.
e. linking against avr-libc). Maybe wrappers will not be needed at all.

I will start with experiments on your branch.

AVR (at least that 8-bit one) would probably need a special handling in some
cases.


Regarding libgcc.a:

I just checked libgcc.a from cross-avr-gcc-4.8.3 and the one I built by "make
all-target" in cross-avr-gcc5-5.1.1+r223279 chroot. Both contain nearly the
same functions (99.9% match). More than 90% of them are helpers for
mathematical functions that compiler can reference. Other interesting are
__main.o, enable-execute-stack.o and few others.

=> Most of these functions are completely independent on target includes. Only
few are. The AVR-failing unwind-dw2.o is one of few exceptions.

I am just guessing that these functions are required even for stage1.

Native libgcc.a has technically very similar contents: about 90% of
mathematical helpers. Just function names are different.