From: Thierry L. <thi...@in...> - 2010-03-12 16:20:57
|
Hi all, This is just to says that patches pr19340.c.patch and gcc4cli_line_info-t-cil32.patch have been commited in our branch. Thierry Lafage. Thierry Lafage a écrit : > Hi all, > > Here are several small patches for our gcc4cli BE branch: > > * *pr19340.c.patch* is to avoid testing with pr19340.c because it > has no sense in cil32 since it tests the scheduler. > * *gcc4cli_line_info-t-cil32.patch* fixes dependencies in t-cil32 > and adds the file source-location.h which was introduced in my > last patch concerning source location (this t-cil32 patch should > have been part of the source location patch). > * *cil-lower.c.patch* modifies the pass gate in order to activate > this pass only when -ftree_vectorize option is activated (which > is the case in -O3) > * and *simp-cond.patch* is a simplification of the simp-cond pass > which also makes it more complete (adds support for > brtrue/brfalse and for floating point comparisons in conditional > branches + add a command-line option which is activated in -O1 + > fixes missing brtrue/brfalse as being conditional branch > instructions). Note that this pass either does nothing, or > change a branch condition instruction into another one (inverts > the condition) and removes the following unconditional branch. > This means that the stack is not changed at all, so I removed > all the stuff that was recomputing the stack at every statement. > Moreover, I didn't understand the test on the conditional branch > operand type (integer or pointer) in order to change the > conditional br instruction: I've removed it and tested on a real > program, and it seems to be ok. More tests are on the way > (check-gcc + cbenchmarks). > > Feel free to comment. I should commit in a few days if you're ok (or > if you don't say anything). > > Regards, > Thierry Lafage. > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > ------------------------------------------------------------------------ > > _______________________________________________ > Gcc4cli-devel mailing list > Gcc...@li... > https://lists.sourceforge.net/lists/listinfo/gcc4cli-devel |