Brecht Sanders MinGW-W64 refrence possibly rather excessive in compiled exe with gcc

[thrive4]

Well first of I ascribe to the notion that 'credit where credit's due'
is given but it seems that when compiled even very simple pieces
of code generate quite a lot of references to:
GCC: (MinGW-W64 i686-posix-sjlj, built by Brecht Sanders) 9.3.0

Take the code I posted in a previous post:
#420
when compiled it contains roughly 4k of references to:
GCC: (MinGW-W64 i686-posix-sjlj, built by Brecht Sanders) 9.3.0
Compile option -s console -w none

The more elaborate the code becomes the higher the
amount, can, be become....

Might be worth looking into because an other
notion worth ascribing to is 'waste not want not' ;)

[SARG-FB]

I posted a solution on the forum.
Did you see it ?

[thrive4]

@sarg Thank you for passing on this solution / workaround!
I've tried it on various projects I have made, and the reduction
in filesize varies to an quite substantial degree.

For instance one case went from ~400KB to ~380KB
a reduction of ~20KB by adding *(.rdata$zzz) as
you suggested.

Just for clarity is there a specific reason why this
is not set in the default build of FB?

I have noticed it completely removes all the references
to GCC: (MinGW-W64 i686-posix-sjlj, built by Brecht Sanders) 9.3.0
I still think one time would be civil, possibly by using a readme.txt
or other external file.

Anyway I will definitely be using this approach, I hope
that it somehow becomes part of the upcoming 1.20
release of FB for now many thanks once again for passing
this info on!

[SARG-FB]

You are welcome.

why this is not set in the default build of FB?

Just because noone seems annoyed by this and file sizes are not a real problem except when loading executable ;-)
Even if I saw that 'garbage' I didn't look to remove it before.
Anyway I posted a message to jeff (lead dev) and I'll see with him the best way to proceed.
And yes adding a text to name Sanders should a good thing.

[jayrm]

Related:
niXman/mingw-builds#412
msys2/MINGW-packages#21

In short, gcc emits an .ident field that adds string text to every module and it isn't merged to one single string in the output. Appears that this can be disabled with gcc -fno-ident ..., but only when compiling from source.

Example comparison of generating .rdata$zzz section or not using -fno-ident gcc option:

> gcc -c a.c && nm a.o
00000000 b .bss
00000000 d .data
00000000 r .rdata$zzz
00000000 t .text
00000000 T _func

> gcc -c a.c -fno-ident && nm a.o
00000000 b .bss
00000000 d .data
00000000 t .text
00000000 T _func

For fbc project itself:

• we can add -fno-ident when building our own libraries (fb, fbgfx, etc)
• we can add it to fbc's gcc options for building with -gen gcc backend
• we don't really care about keeping the .ident for our own stuff and our licensing doesn't require it

For the supporting libraries from the prebuilt toolchain:

• next fbc release will have a binary package based on mingw-w64-gcc-11.2.0.
• see https://github.com/niXman/mingw-builds-binaries/releases/tag/11.2.0-rt_v9-rev1
• this toolchain appears to have the supporting libraries built with -fno-ident

[thrive4]

All righty...
First many thanks to both sarg-fb and jayrm aka coderjeff
for looking into this and the effort for coming up with possible
solutions / workarounds.

I had a slight suspicion that there would be more to this
then meets the eye, good to read about the licensing
specific aspect, and hope that the '-fno-ident' option
resolves this issue for all parties concerned.

So the *(.rdata$zzz) mod to fbextra.x as sarg aka sarg-fb
suggested for fbc 1.09 ~ fb 1.10
https://www.freebasic.net/forum/viewtopic.php?t=32254&start=45
and from fbc 1.20 compiling with'-fno-ident' will suffice?

Bye the bye since 2014...
msys2/MINGW-packages#21
Sic Parvis Magna...

[jayrm]

@thrive4

and from fbc 1.20 compiling with '-fno-ident' will suffice?

Not entirely.
Depends on the toolchain used to compile any of the supporting static libraries or object modules. If the supporting libraries were compiled with the .ident string, then -fno-pic -fno-ident won't remove those.

We could add discarding *(.rdata$zzz) to fbextra.x for fbc 1.20.0, but it would be nice to know if anything important gets stored there.

Edit: oops, meant to write -fno-ident above instead of -fno-pic.

[Rinat84]

Something like this.
Excluded FFI, compiled for example.
freebasic.zip

[jayrm]

Added gcc option -fno-ident when compiling under windows:
In fbc-1.20.0 see commit: [e6bc5cc]

In hindsight, I should have probably added to fbc-1.10.1 branch first and then merged in to fbc-1.20. So instead, I will follow this up with a cherry-pick to fbc-1.10.1 and then a merge later.

[jayrm]

fbc-1.20.0 commit: [e6bc5cc] cherry picked to
fbc-1.10 branch in commit: [a146bd8]

Next releases will have the -fno-ident option by default for windows.

I believe we can consider this issue closed.