AkelPad

Diamen wrote: ↑Sat May 02, 2026 7:52 pmto reduce dll size

Diamen wrote: ↑Sat May 02, 2026 7:52 pm

Code: Select all

fbc -dll -gen gcc -arch x86_64 -x "SmartMath.dll" -strip -O 2 -Wc -Os "SmartMath.bas" "SmartMath_Config.bas" "SmartMath_Format.bas" "SmartMath_CopyNormalize.bas" "SmartMath_About.bas" "SmartMath_Menu.bas" "MathParser.bas"

to reduce dll size.

1. Option 1: Prioritize Performance (Speed)
   If the DLL performs heavy calculations or logic where speed is critical, use -O 2 or -O 3 and remove the size optimization.
   It tells GCC to prioritize execution speed, even if it makes the file slightly larger by unrolling loops or inlining functions.
   Result: Faster execution, slightly larger file.
   The revised command (Standard Balance):
   fbc -dll -gen gcc -arch x86_64 -x "my.dll" -strip -O 2 "my.bas"
   The revised command (Max Speed):
   fbc -dll -gen gcc -arch x86_64 -x "my.dll" -strip -O 3 "my.bas"
2. Option 2: Prioritize Smallest File Size
   If the DLL is simple or needs to be as lightweight as possible (e.g., for web distribution or embedded use), keep -Os and remove the general optimization flag.
   It enables all -O2 optimizations that don't increase code size, then adds specific passes to shrink the binary further.
   Result: Smallest possible .dll file, moderate execution speed.
   The revised command:
   fbc -dll -gen gcc -arch x86_64 -x "my.dll" -strip -Wc -Os "my.bas"

Diamen wrote: ↑Sun May 03, 2026 4:24 am Note that fbc -O 2 -Wc -O2 is redundant...

1. Stage 1: FreeBASIC (-O 2)
   Translates your .bas code into .c (C source code).
   The Benefit: -O 2 tells FB to write "smart" C code.
   It optimizes how it handles BASIC-specific things like array lookups, string memory, and variable scopes.
2. Stage 2: GCC (-Wc -O2)
   Translates that .c code into a .dll (Machine code).
   The Benefit: -Wc -O2 tells GCC to use its own advanced logic to optimize the machine code.
   It handles CPU-level things like instruction scheduling, register allocation, and branch prediction.

• If you remove -O 2:
  FreeBASIC will generate "lazy" C code.
  Even if GCC is set to -O2, it has to work much harder to fix the unoptimized C code, and the final result will likely be slower.
• If you remove -Wc -O2:
  FreeBASIC will write great C code, but GCC will compile it with no optimization (Level 0).
  This results in a "heavy," slow DLL because the final machine code hasn't been streamlined for the CPU.

ewild wrote: No, it is not redundant.

ewild wrote: ↑Sun May 03, 2026 10:29 am DV
With the latest updates, I can no longer build a working SmartMath.dll from your sources.
Upon its call, SmartMath.dll immediately crashes AkelPad.

Diamen wrote: ↑Sun May 03, 2026 12:48 pm Work fine here for me.

Diamen wrote: ↑Sun May 03, 2026 12:48 pm FreeBASIC-1.10.1-win64.7z

windres -F pe-x86-64 -c 65001 -I "%FB_HOME%\inc\win\rc" -i SmartMath.rc -o "%OUT_DIR%\SmartMath_res.o"

ewild wrote: ↑Sun May 03, 2026 2:17 pm So, I started removing any previous SmartMath settings, and when I deleted its Registry entry, your DLL began working, and so did mine, too.

parameter :: visible value          :: type                               :: result 
Color     :: dword:00008000 (32768) :: REG_BINARY: Raw binary data [hex:] :: SmartMath/AkelPad crash
Color     :: 32768                  :: REG_SZ: Standard string [hex(1)]   :: OK

Diamen wrote: ↑Sun May 03, 2026 2:56 pm I used previous...

Diamen wrote: ↑Sun May 03, 2026 7:12 pmCompile64.bat refer to "%FB_HOME%\bin\win32" but for me work "%FB_HOME%\bin\win64".