Re: [google] Specify target as ix86 or x86_64 for test builtin_target.c (issue5174041)

2011-09-30 Thread Richard Henderson
On 09/30/2011 02:09 PM, Sriraman Tallam wrote: > * testsuite/gcc.dg/builtin_target.c: Specify target as ix86 or > x86_64. > > Index: gcc.dg/builtin_target.c > === > --- gcc.dg/builtin_target.c (revision 179400) > +++ gcc

Re: [google] Specify target as ix86 or x86_64 for test builtin_target.c (issue5174041)

2011-09-30 Thread Sriraman Tallam
Moving test gcc.target/i386 * testsuite/gcc.dg/builtin_target.c: Remove. * testsuite/gcc.target/i386/builtin_target.c: New file. On Fri, Sep 30, 2011 at 2:33 PM, Richard Henderson wrote: > On 09/30/2011 02:09 PM, Sriraman Tallam wrote: >>       * testsuite/gcc.dg/builtin_target.c

Re: [PATCH] Add sparc VIS 2.0 builtins, intrinsics, and option to control them.

2011-09-30 Thread Joseph S. Myers
On Fri, 30 Sep 2011, Richard Henderson wrote: > Specifically, in-compiler support for #pragma STDC FENV_ACCESS and the > various routines. We ought to be able to track the rounding > mode (and other relevant parameters) on a per-expression basis, tagging > each floating-point operation with the

Re: [PATCH] Add sparc VIS 2.0 builtins, intrinsics, and option to control them.

2011-09-30 Thread David Miller
From: Richard Henderson Date: Fri, 30 Sep 2011 14:03:52 -0700 > (3) Use optimize-mode-switching to minimize the number of changes > to the global state. This includes the use of SIAM vs %fsr, > especially when a subroutine call could have changed the > global rounding mode.

Re: Commit: RX: Add support for MIN and MAX instructions in QI and HI modes

2011-09-30 Thread Richard Henderson
On 09/28/2011 07:34 AM, Nick Clifton wrote: > -(define_insn "smaxsi3" > - [(set (match_operand:SI 0 "register_operand" "=r,r,r,r,r,r") > - (smax:SI (match_operand:SI 1 "register_operand" "%0,0,0,0,0,0") > - (match_operand:SI 2 "rx_source_operand" > -

[PATCH] Don't assume that constants can clobber vtbl

2011-09-30 Thread Maxim Kuvyrkov
This patch makes detect_type_change analysis assume that only ADDR_EXPRs can be assigned to vtable entries. Initially, the patch made a less strict assumption that constants are not assigned to vtables. I then bumped the assumption to "only ADDR_EXPRs can be assigned to vtables". I have this

Disable early inlining while compiling for coverage (issue5173042)

2011-09-30 Thread Sharad Singhai
This patch disables early inlining when --coverage option is specified. This improves coverage data in presence of other optimizations, specially with -O2 where early inlining changes the control flow graph sufficiently enough to generate seemingly very odd source coverage. Bootstrapped okay and r

[google] Fix bugs in sampled profile collection

2011-09-30 Thread Easwaran Raman
This fixes two issues with sampled profile collection. It delays cleanup of instrumentation_to_be_sampled after all callgraph nodes have been instrumented and prevents gcov_sample_counter_decl and gcov_sampling_rate_decl from being garbage collected. Ok for google/gcc-4_6 and google/main branche

Re: [google] Fix bugs in sampled profile collection

2011-09-30 Thread Xinliang David Li
ok. David On Fri, Sep 30, 2011 at 6:54 PM, Easwaran Raman wrote: > This fixes two issues with sampled profile collection. It delays > cleanup of instrumentation_to_be_sampled after all callgraph nodes > have been instrumented and prevents  gcov_sample_counter_decl and > gcov_sampling_rate_decl f

Re: Disable early inlining while compiling for coverage (issue5173042)

2011-09-30 Thread Xinliang David Li
Yes, this will improve test coverage option's usability, but please provide the example to explain the issues. David On Fri, Sep 30, 2011 at 6:12 PM, Sharad Singhai wrote: > This patch disables early inlining when --coverage option is > specified. This improves coverage data in presence of other

Re: Disable early inlining while compiling for coverage (issue5173042)

2011-09-30 Thread शरद सिंघई
Here is an example. In the attached file, foo.c contains only two functions, 'sum' and 'main'. The function 'sum' gets inlined into 'main' (with -O2). gcc --coverage -O2 foo.c ./a.out gcov -b foo.c Now the coverage data for the 'if' condition in 'sum' looks like this: (in attached file foo.c.gcov

[patch] --enable-dynamic-string default for mingw-w64 v2

2011-09-30 Thread JonY
Hi, I followed Paolo's suggestion with the os_defines.h trick. I duplicated os/mingw32/ to os/mingw32-w64/ for this to work, since there aren't any built-in defines to tell the 2 apart unless you include some headers like _mingw.h. Patch attached, comments? Index: configure.host =

Re: [Mingw-w64-developer] [patch] --enable-dynamic-string default for mingw-w64 v2

2011-09-30 Thread Ozkan Sezer
On Sat, Oct 1, 2011 at 9:03 AM, JonY wrote: > Hi, > > I followed Paolo's suggestion with the os_defines.h trick. I duplicated > os/mingw32/ to os/mingw32-w64/ for this to work, since there aren't any > built-in defines to tell the 2 apart unless you include some headers > like _mingw.h. > > Patch

<    1   2