Re: [ada, build] host/target configuration

2013-06-02 Thread Eric Botcazou
> So, your case works because the manu/osys parsing wrongly detects/assigns > a manufacturer »linux« and an operating system androideabi. Then, the > following case fails, which is expected to yield identical results, with > "complete triplets" -- which I took for granted in my reasoning about the

Re: Patch ping - Add a new option "-fstack-protector-strong"

2013-06-02 Thread Gerald Pfeifer
On Fri, 26 Apr 2013, Han Shen(沈涵) wrote: > Hi, I'd like to ping the patch '-fstack-protector-strong': > > - http://gcc.gnu.org/ml/gcc-patches/2013-04/msg00945.html > Add a new option '-fstack-protector-strong' to protect only > stack-smashing-vulnerable functions. I see this is now in? Can you

Re: [PATCH RX] Added target specific macros for macros for RX100, RX200, and RX600

2013-06-02 Thread Gerald Pfeifer
On Thu, 2 May 2013, Sandeep Kumar Singh wrote: > 2013-05-02 Sandeep Kumar Singh > > * rx/rx.h (TARGET_CPU_CPP_BUILTINS): Add macros for RX100, RX200, and > RX600. > * rx/rx.opt: Add macro for rx100 with string rx100 and value RX100. > * rx/rx-opts.h (rx_cpu_types): Add new c

Re: [ada, build] host/target configuration

2013-06-02 Thread Alexandre Oliva
On May 31, 2013, Olivier Hainque wrote: > - revert to our former computations, based on target and >not target_alias. Revert the subsequent adjustments as >well. *nod* > - Use target_alias explicitly just at the points where >we know that we need to depart from the canonical name

[PATCH] Basic support for MIPS r5900

2013-06-02 Thread Jürgen Urban
Hello, after some months I reworked the patch for r5900. It would be nice if this could be accepted. The patch contains only changes to get basic support for MIPS r5900. It can be used to compile a working Linux kernel for the Playstation 2. It is also possible to get Linux programs working wit

Re: [GOOGLE] Unrestrict early inline restrictions for AutoFDO

2013-06-02 Thread Dehao Chen
The patch was committed to google-4_8, but it causes problem because einline sets PARAM_EARLY_INLINING_INSNS = 11. This will cause recursive inlining at einline stage (e.g. main->foo, foo->bar, bar->foo) when autofdo is enabled. The following patch can fix the problem by doing more targetted early

[PATCH][1 of 2] Add value range info to SSA_NAME for zero sign extension elimination in RTL

2013-06-02 Thread Kugan
Hi, This patch adds value range information to tree SSA_NAME during Value Range Propagation (VRP) pass in preparation to removes some of the redundant sign/zero extensions during RTL expansion. This is based on the original patch posted in http://gcc.gnu.org/ml/gcc-patches/2013-05/msg00610.

Re: [GOOGLE] Unrestrict early inline restrictions for AutoFDO

2013-06-02 Thread Xinliang David Li
auto profile info is not available yet in early inlining, why would this change make any difference? Can you just reset the max_iters to a higher value for autoFDO? David On Sun, Jun 2, 2013 at 6:21 PM, Dehao Chen wrote: > The patch was committed to google-4_8, but it causes problem because > ei

[PATCH][2 of 2] RTL expansion for zero sign extension elimination with VRP

2013-06-02 Thread Kugan
Hi, This patch removes some of the redundant sign/zero extensions using value range information during RTL expansion. When GIMPLE_ASSIGN stmts with LHS type smaller than word is expanded to RTL, if we can prove that RHS expression value can always fit in LHS type and there is no sign conver

Re: [GOOGLE] Unrestrict early inline restrictions for AutoFDO

2013-06-02 Thread Dehao Chen
On Sun, Jun 2, 2013 at 7:14 PM, Xinliang David Li wrote: > > auto profile info is not available yet in early inlining, why would > this change make any difference? Because the check of PARAM_EARLY_INLINING_INSNS is after the check of cgraph_maybe_hot_edge_p in early inline. If cgraph_maybe_hot_ed

[ACTIVITY] 10-14 May 2013

2013-06-02 Thread Kugan
== Progress == * VRP based zero/sign extension - Tested and posted the latest patch * Better end of loop counter optimisation - Tree level optimization are optimized in mainline - Christophe noted a slight change in asm generated from earlier version - tracked down the patch causing this

Re: [ACTIVITY] 27-31 May 2013

2013-06-02 Thread Kugan
Apologies for sending again. Corrected wrong dates in subject now. On 03/06/13 12:19, Kugan wrote: == Progress == * VRP based zero/sign extension - Tested and posted the latest patch * Better end of loop counter optimisation - Tree level optimization are optimized in mainline - Christo

Re: [GOOGLE] Unrestrict early inline restrictions for AutoFDO

2013-06-02 Thread Xinliang David Li
If the purpose of the fix is to filter early inlinings with code growth in autoFDO, the proposed fix is the wrong way to do -- it changes the meaning of cgraph_maybe_hot_edge_p. David On Sun, Jun 2, 2013 at 7:25 PM, Dehao Chen wrote: > On Sun, Jun 2, 2013 at 7:14 PM, Xinliang David Li wrote: >>

Re: [GOOGLE] Unrestrict early inline restrictions for AutoFDO

2013-06-02 Thread Dehao Chen
I've updated the patch to check it at ipa-inline: Index: gcc/ipa-inline.c === --- gcc/ipa-inline.c (revision 199593) +++ gcc/ipa-inline.c (working copy) @@ -434,6 +434,16 @@ want_early_inline_function_p (struct cgraph_edge * i

Re: [GOOGLE] Unrestrict early inline restrictions for AutoFDO

2013-06-02 Thread Xinliang David Li
The patch is ok if performance test passes. For a complete fix, Is it better to tune down PARAM_EARLY_INLINE_INSNS from 11 to a small value for autoFDO or use a different parameter? David On Sun, Jun 2, 2013 at 9:19 PM, Dehao Chen wrote: > I've updated the patch to check it at ipa-inline: > > I