IRC channel logs
2013-07-01.log
back to list of logs
<civodul>in nix-daemon.cc, can you add some printfs? :-) <Steap>settings.useSubstitutes is set to "0" in "case wopSetOptions" <bubu>most stupid film i watched for months :/ <bubu>too bad all other (decent) films were full at the time i went to the cinema... <bubu>hum civodul you're an autotools expert i guess ? <bubu>because i have some optimization issues <bubu>i have split my project in two parts <bubu>and a command line interface in src/ <bubu>the thing is that it highly vectorizable (4 levels of loops performing additions and multiplications) <bubu>so I have my code in a .a <bubu>and link it to the binary build in src/ <bubu>but gcc doesn't optimize this well <bubu>if now i build everything in a single binary it seems to work <civodul>hey, that's not an autotools question, is it? :-) <bubu>instead of LDADD = ../lib/mylib.la <bubu>if i project_SOURCES = ../lib/files.c <civodul>so run "make clean && make CFLAGS="-g -O2 -flto" LDFLAGS=-flto" <bubu>but i'm suspecting it is because for building the library gcc cannot inline too much or something like <bubu>all symbols must be exported no ? <bubu>I would like to have only the symbol in my _public.h header <bubu>so I guess I should everything else properly organised in files and static all the functions ? <civodul>well, if the lib contains LTO objects, then it can perform inlining & co. in the final binary <bubu>yes I added flto both in cflags and ldflags <civodul>functions have to be either static or __attribute__((hidden)) to be subject to inlining <bubu>hum, yes i suspected something like this so i have to figure out how to properly handle this for functions between files that i don't want to export <bubu>well seems ok if i handle this properly <bubu>is there a way to display the build process in a more synthetic way ? <bubu>but otherwise i must admit it seems quite good <bubu>i yet didn't understand how to properly make a "release" archive containing the configure etc... and the sources files <bubu>but they are also very dense ! <bubu>nevertheless more doc in better than less ! <bubu>next step will be texinfo <bubu>putting everything in big columns <bubu>and heating the room with the cpu looping on them <bubu>it's octave-like in a sense <bubu>i was impressed by new intel cpus and SIMD <bubu>and gcc to use them quite properly <bubu>I didn't find a way to use -std=gnu11 instead of gnu99 i suppose this will come in an ulterior version ? <civodul>and you've not seen "make distcheck" yet! ;-) <bubu>but how to make the auto* to use it ? <bubu>c11 or gnu11 instead of gnu99 <civodul>ah, just add AM_CFLAGS = -std=c11 in a Makefile.am <bubu>how is the work on guix going on ? <civodul>with cross-compilation in place, we're close to the next release <civodul>and then closer to a bootable thing as well ;-) <bubu>really willing to try this an OS without mixing package managers