On 03/09/2016 05:42 PM, Dimitry Sibiryakov wrote:
> 09.03.2016 15:33, Vlad Khorsun wrote:
>>      Compare it with v2.5 build system.
>     2.5 build is about two times faster.
>
>> Also, tell to yourself how much faster it could be
>> if you apply patch you are talking about.
>     According to VS build timing, it should save me about 10 minutes

Dmitry - I'm surprised much with that time. What 386 box are you 
building on? :)
I have 3 or 4 years old Amd 8120 and full build of btyacc takes 0.3 sec. 
Yes it's linux not windows but build time should not differ _so_ much.
Looks like something seriously wrong with your build machine...

*******************************************
FYI:
localhost btyacc # make clean
rm -f closure.o error.o lalr.o lr0.o main.o mkpar.o output.o mstring.o 
reader.o readskel.o skeleton.o symtab.o verbose.o warshall.o

localhost btyacc # time make -j8
cc    -c -o closure.o closure.c
cc    -c -o error.o error.c
cc    -c -o lalr.o lalr.c
cc    -c -o lr0.o lr0.c
cc    -c -o main.o main.c
cc    -c -o mkpar.o mkpar.c
cc    -c -o output.o output.c
cc    -c -o mstring.o mstring.c
cc    -c -o reader.o reader.c
cc    -c -o readskel.o readskel.c
cc    -c -o skeleton.o skeleton.c
cc    -c -o symtab.o symtab.c
cc    -c -o verbose.o verbose.c
cc    -c -o warshall.o warshall.c
cc  -o btyacc closure.o error.o lalr.o lr0.o main.o mkpar.o output.o 
mstring.o reader.o readskel.o skeleton.o symtab.o verbose.o warshall.o
main.o: In function `create_file_names':
main.c:(.text+0x782): warning: the use of `mktemp' is dangerous, better 
use `mkstemp'

real    0m0.310s
user    0m1.062s
sys     0m0.178s
localhost btyacc #


------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to