Michaell

For the audience which is finding this old topic here my experience: regarding 1): If you have no good reason to switch the compiler: Don't do it, it will cost you weeks of work and at the end you will have a big disadvantage at 2). regarding 2): please see this information

I'm currently using C++ Builder Athens 12.2 and switched from bcc32 to bcc32c. Following my finding regarding the huge compile time differences. All values are rounded (max. +/- 3 s) and measured several times. CPU Ryzen 5 5600X: bcc32: 25 s, 1 CPU thread bcc32c: around 40 minutes, 1 CPU thread bcc32c: 170 s, 12 CPU threads Due to this bad result I upgraded my CPU. CPU Ryzen 9 5950X: bcc32: not measured bcc32c: 120 s, 12 CPU threads bcc32c: 80 s, 32 CPU threads May be these information may help other users in view of compiler switch and or CPU switch. Greetings! Michaell

to close this topic: I found no solution with my existing project (-settings) and decided to start from scratch. This was also a pain but finally it worked.

Is this my problem?: If yes, what has to be changed in the project options?

The help for the bcc32c.exe can be obtained via the CLI: ...\bin\bcc32c.exe -cc1 --help It list these two object file related options (and others which are may be also relevant?): -emit-obj -mincremental-linker-compatible I tried both but again no success, I really do not get it. 😕 Btw.: One of my initial questions was "Where is the '-cc1' compiler option?" (to try to remove it). The now available help tells that this is always the 1st parameter i.e. must be present.

-tWM -o The '-o' was inserted by me. Due to this I tried again to remove all "Additional Options to pass to the compiler". Now it is really empty and it still compiles. Whatever the problem at my 1st try was, now its gone but it does not help for the original problem.

I already deleted most of them, until it was no longer compiling.

1) I'm not able to see unexpected options because I'm not aware what expected options are. I checked the existing options and I guess they are OK. 2) As I wrote above: The missing files are nowhere, i.e. also not in '...\Win32\Debug\' which is currently set in 'C++ Shared options | Intermediate output'. FYI: I have removed my '...\OBJ_test\' folder and cleaned the related project option, i.e. I expect now the object files in '...\Win32\Debug\'.

I have "played" for hours with the GUI presented options w/o success, obviously it makes no sense if there is no (full) understanding of its purpose and the Clang (Embarcadero) help is not helping me. I decided then to ask "the forum" in the hope to find an experienced user.

I'm using version 12.2, see also my set tags. Here is an example of a Clang call for 1 file: bcc32c command line for "_Main\_MainWin.cpp" c:\program files (x86)\embarcadero\studio\23.0\bin\bcc32c.exe -cc1 -D _DEBUG -D DEBUG -D FRAMEWORK_VCL -output-dir .\OBJ_test -I "c:\program files (x86)\embarcadero\studio\23.0\include" -I D:\... -I "C:\Program Files (x86)\..." -I <pathsRemoved> "c:\program files (x86)\embarcadero\studio\23.0\include" -isystem "c:\program files (x86)\embarcadero\studio\23.0\include\dinkumware64" -isystem "c:\program files (x86)\embarcadero\studio\23.0\include\windows\crtl" -isystem "c:\program files (x86)\embarcadero\studio\23.0\include\windows\sdk" -isystem "c:\program files (x86)\embarcadero\studio\23.0\include\windows\rtl" -isystem C:\Users\Public\Documents\Embarcadero\Studio\23.0\hpp\Win32 -isystem "c:\program files (x86)\embarcadero\studio\23.0\include\windows\vcl" -isystem "c:\program files (x86)\embarcadero\studio\23.0\include\windows\fmx" -isystem C:\Users\Public\Documents\Embarcadero\Studio\23.0\hpp\Win32 -debug-info-kind=standalone -fborland-define-external-types -fcxx-exceptions -fborland-extensions -nobuiltininc -nostdsysteminc -triple i686-pc-windows-omf -emit-obj -mrelocation-model static -masm-verbose -ffunction-sections -fexceptions -fseh -mstack-alignment=16 -fno-spell-checking -fno-use-cxa-atexit -fno-threadsafe-statics -main-file-name _MainWin.cpp -x c++ -std=c++17 -O0 -fmath-errno -tM -tW -o .\OBJ_test\_MainWin.obj --auto-dependency-output -MT .\OBJ_test\_MainWin.obj -tWM -Wno-writable-strings -Wno-format -object _Main\_MainWin.cpp Success Elapsed time: 00:00:05.2 In my output directory "\OBJ_test" and all other directories is no *.o or *.obj present. I guess the Clang compiler has a wrong option defined (as visible above, there are a lot of them), unfortunately I have no experiences with it.

Hello, my project was made with the legacy classic Borland compiler. Now I have tried the Clang compiler (32 bit Windows) after some work all of my *.cpp files can be compiled but after the compile there are only <fileName>.#00 and <fileName>.d instead of <fileName>.obj files present. The compiler options '-o' or '-object' did not change anything. I found this stackoverflow.com thread for some equal problem. It tells (e.g.) to remove the '-cc1' option (I do not use (intentionally) any plugin). I would like to try it, but cannot find it in the Embarcadero C++ Builder project options GUI. 1) Where is the '-cc1' compiler option? 2) What can I do else to get the object files? Thanks a lot! Michaell

@weirdo12 I had today the same Clang problem, thanks for your post.

You mentioned both and both is using the same IDE.

No more C++ Builder crashes at debugging.

Solution at my system, modify via regedit: HKEY_CURRENT_USER\Software\Embarcadero\BDS\23.0\Debugging\HighlightDebugWindows from True to False