Diskussions- und Newsboard des DARC-Ortsverbandes I40
allgemeine Kategorie => UHSDR Firmware => Message started by: DF8OE on 28. December 2018, 11:07:23

Title: gcc-8-branch revision 267074
Post by: DF8OE on 28. December 2018, 11:07:23

Hi to all,

I just installed the brand new gcc (release on 20th of December) and compared size of binary to the last version of the compiler.

and - surprise, surprise - here the result:

fw-mchf.bin, full build:
old gcc: 479712 bytes
new gcc: 410728 bytes

Nothing changed - only use of newest gcc... Very interesting and nice to see. So our full build fits again in 512KB MCU.

vy 73
Andreas

Title: Re:gcc-8-branch revision 267074
Post by: DB4PLE on 28. December 2018, 12:34:24

Hi Andreas,

I just noticed the release of the new compiler, too. Interestingly it did not change much on the F7/H7 resulting binary sizes although basically the same processor instruction set is used...

73
Danilo


Title: Re:gcc-8-branch revision 267074
Post by: DF8OE on 28. December 2018, 12:50:19

Hi Danilo,

yes - I noticed that, too. Very interesting. May be 2-update was a little bit confused at F4. I do not habe compared object files. Possibly this is a linker and not a compiler result...

vy 73
Andreas

Title: Re:gcc-8-branch revision 267074
Post by: DB4PLE on 28. December 2018, 14:16:48

Hi Andreas,

I think, no, we use same linking strategy on all machines in Makefile. Of course, there could be something subtle in some of the settings, but they look very, very similar.

73
Danilo



Title: Re:gcc-8-branch revision 267074
Post by: DF8OE on 28. December 2018, 14:20:06

Hi Danilo,

I know. But I am not able to see in a quick way was is going on internally in gcc software. There must be something that is working different on -q2-update and -q4-major and on F4 <--> F7/H7... I already have tested resulting binaries on all processor types and everything looks fine.

vy 73
Andreas

Title: Re:gcc-8-branch revision 267074
Post by: DB4PLE on 28. December 2018, 14:55:49

Hi,

good, then make this the default compiler for builds. However, at least on Windows we have issues with building in Eclipse and this compiler (more precisely the linker).

73
Danilo

Title: Re:gcc-8-branch revision 267074
Post by: DF8OE on 28. December 2018, 15:23:20

Hi Danilo,

of course I am following the discussion and I want to test if Eclipse @Linux is doing the job. I haven't used Eclipse since months :P. How can I set quickly a new path for toolchain so that I can switch fast between different toolchains? Is there any non-project related setting which overrides all project specific setting?

vy 73
Andreas

Title: Re:gcc-8-branch revision 267074
Post by: DB4PLE on 28. December 2018, 17:21:30

Hi Andreas and others,

changing the paths is simple in Eclipse, just go to Window->Preferences->MCU-> ...
See https://github.com/df8oe/UHSDR/wiki/Windows-10-x64-Compiler-Setup-and-Build-Environment#setting-up-everything-in-eclipse (https://github.com/df8oe/UHSDR/wiki/Windows-10-x64-Compiler-Setup-and-Build-Environment#setting-up-everything-in-eclipse). Basically applies to Linux as well. You don't need to set the build tools path normally, these are standard linux tools.

73
Danilo


Diskussions- und Newsboard des DARC-Ortsverbandes I40 | Powered by YaBB SE
© 2001-2003, YaBB SE Dev Team. All Rights Reserved.