Hi,

>> 2010-03-10 14:34 UTC+0100 Viktor Szakats (harbour.01 syenar.hu)
>>  * config/win/cygwin.mk
>>  * config/win/mingw.mk
>>  * config/wce/mingwarm.mk
>>    % Added -pipe option to win/gcc compilers, this way it's faster 
>>      (but consume more memory) since it passes intermediate files 
>>      - I could only spot the .s file - without writing them to disk.
>>      Probably we should enable this on other platforms as well,
>>      and if it works out well, also in hbmk2.
> 
> I'm using -pipe for 10 or even more years in different Linux distros
> and it works quite well.
> The only one drawback in using -pipe is problem with compilation errors.
> Sometimes it may cause that unfinished and broken destination files are
> created because compilation/link process is interrupted by compile time
> errors.
> There was a time when this option was enabled in xharbour.spec indirectly
> by RPM_OPT_FLAGS and I removed it due to problems with compile time errors
> which caused that wrong/unfinished binary files were processed:
> 
>   2003-08-09 22:18 UTC+0200 Przemyslaw Czerpak <[email protected]>
>     * xharbour/xharbour.spec
>       * removed ${RPM_OPT_FLAGS} from C_USR
>         '-pipe' breaks building proces on RH9 when user doesn't install
>         old slang-devel
> 
> what disabled hidden functionality which allowed to build xHarbour
> without some libraries (errors were ignored).
> Anyhow it should not be a problem for current Harbour build process
> because now all errors interrupt it immediately.

So I assume it's safe to add it for gcc on other platforms 
as well. Any limitations here? F.e. does OS/2 or DJGPP support it?

> Maybe you only should check it for hbmk2 and if necessary add code
> to explicitly delete unfinished destination files on errors.

I did a very simple test with one good and one broken .c input 
file (with mingw only), but couldn't spot a difference in behavior 
when using -pipe. The .o file for the right one was created, 
for the wrong one, it wasn't.

Brgds,
Viktor

_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to