Re: Avoiding some garbage rtl from instantiate_virtual_regs

Jeff Law writes: >> Index: gcc/emit-rtl.h >> === >> --- gcc/emit-rtl.h 2014-05-15 11:27:06.000259353 +0100 >> +++ gcc/emit-rtl.h 2014-05-16 09:11:42.479556294 +0100 >> @@ -52,10 +52,10 @@ extern tree get_spill_slot_decl (bool); >>

Re: RFC: Faster for_each_rtx-like iterators

Thanks for the comments. Jeff Law writes: >> Implementation-wise, the main observation is that most subrtxes are part >> of a single contiguous sequence of "e" fields. E.g. when compiling an >> oldish combine.ii on x86_64-linux-gnu with -O2, we iterate over the >> subrtxes of 7,636,542 rtxes. O

Re: Eliminate write-only variables

* gcc.target/ia64/visibility-1.c (variable_i): Add used attribute. diff --git a/gcc/testsuite/gcc.target/ia64/visibility-1.c b/gcc/testsuite/gcc.target/ia64/visibility-1.c index fdccab3..354f081 100644 --- a/gcc/testsuite/gcc.target/ia64/visibility-1.c +++ b/gcc/testsuite/gcc.target/ia64/

Re: [PATCH] Fix more typos in error messages

Jeff Law writes: > On 02/25/14 09:21, Benno Schulenberg wrote: >> 2014-02-07 Benno Schulenberg >>> >>> * config/arc/arc.c (arc_init): Fix typo in error message. >>> * config/i386/i386.c (ix86_expand_builtin): Likewise. >>> (split_stack_prologue_scratch_regno): Likewise. >>> * for

RE: [PATCH][MIPS] Implement O32 FPXX ABI (GCC)

Hi Richard, I know we are bombarding you with quite large features but if you have chance to comment on this patch it would be useful. There is only one further major patch to post and then all recent work from Imagination will be visible. Once I've sent that out we should probably discuss the or

Replace C/C++ void_zero_node with a VOID_CST tree code

The main thing keeping zero-precision wide-ints alive was void_zero_node, a tree used in the C and C++ frontends that has type VOID_TYPE but code INTEGER_CST. Richard B. asked me to replace the INTEGER_CST with a new constant type, here called VOID_CST. Most of it is straight-forward. The one pe

Re: [PATCH][MIPS] Implement O32 FPXX ABI (GCC)

Matthew Fortune writes: > Hi Richard, > > I know we are bombarding you with quite large features Yeah :-) Please bear in mind I'm doing this in my spare time and this kind of thing takes in the order of hours to review properly. I'd been prioritising the binutils patches because those can go in

Re: [PATCH] Fix more typos in error messages

> FAIL: gfortran.dg/complex_intrinsic_4.f90 -O ... Same failures also for complex_intrinsic_6.f90. Fixed with the following patch --- ../_clean/gcc/fortran/check.c 2014-05-16 23:41:02.0 +0200 +++ gcc/fortran/check.c 2014-05-17 05:05:20.0 +0200 @@ -1821,8 +1821,8 @@ gfc_chec

Re: [wide-int] Add fast path for hosts with HWI widening multiplication

Richard Henderson writes: > On 05/08/2014 01:12 PM, Richard Sandiford wrote: >> * wide-int.cc: Only include longlong.h if W_TYPE_SIZE==32 or >> __SIZEOF_INT128__ is defined. > > FWIW, this looks pretty good to me. Thanks, belatedly applied. Richard

Re: we are starting the wide int merge

Gerald Pfeifer writes: > On Sat, 10 May 2014, Gerald Pfeifer wrote: >> Since (at least) 16:40 UTC that day my i386-unknown-freebsd10.0 builds >> fail as follows: >> >> Comparing stages 2 and 3 >> warning: gcc/cc1obj-checksum.o differs >> warning: gcc/cc1-checksum.o differs >> warning: gcc

Re: [PATCH] Fix ARM NAN fraction bits

On May 17, 2014 12:22:23 AM CEST, "Maciej W. Rozycki" wrote: >On Fri, 16 May 2014, Joseph S. Myers wrote: > >> > 2014-05-16 Maciej W. Rozycki >> > >> >PR libgcc/60166 >> >* sysdeps/arm/soft-fp/sfp-machine.h (_FP_NANFRAC_S, _FP_NANFRAC_D) >> >(_FP_NANSIGN_Q): Set the quiet bit. >>

Re: Replace C/C++ void_zero_node with a VOID_CST tree code

Richard Sandiford writes: > The main thing keeping zero-precision wide-ints alive was void_zero_node, > a tree used in the C and C++ frontends that has type VOID_TYPE but code > INTEGER_CST. > > Richard B. asked me to replace the INTEGER_CST with a new constant type, > here called VOID_CST. Most

Re: Make check_effective_target_vect_sizes_32B_16B handle -mprefer-avx128

On Sat, May 10, 2014 at 6:00 PM, Joseph S. Myers wrote: > In general, vectorization tests whose expectations on x86 depend on > whather AVX is available should only consider AVX available if > -mprefer-avx128 is not enabled. Some of the effective-target > functions in target-supports.exp handle t

Re: [patch ping] libstdc++ testsuite cxxflags

On 17 May 2014 01:16, Sandra Loosemore wrote: > It appears that this patch from last fall never got reviewed. > > https://gcc.gnu.org/ml/gcc-patches/2013-10/msg02340.html > > Can someone take a look? I'll commit the patch on Cesar's behalf if it's > approved. Libstdc++ patches need to go to the l

Re: [patch ping] libstdc++ testsuite cxxflags

On 17 May 2014 10:50, Jonathan Wakely wrote: > Then archives's inability... Oof, not sure what my fingers were thinking there, I meant "Then the archive's inability..." :)

Re: [PATCH, PR58066] preferred_stack_boundary update for tls expanded call

On Mon, May 12, 2014 at 7:38 PM, Wei Mi wrote: >>> Here is a patch for the test. It contains two changes: >>> 1. For emutls, there will be an explicit call generated at expand >>> pass, and no stack adjustment is needed. So add /* { >>> dg-require-effective-target tls_native } */ in the test. >>>

Re: [patch ping] libstdc++ testsuite cxxflags

On 17 May 2014 10:50, Jonathan Wakely wrote: > On 17 May 2014 01:16, Sandra Loosemore wrote: >> It appears that this patch from last fall never got reviewed. >> >> https://gcc.gnu.org/ml/gcc-patches/2013-10/msg02340.html >> >> Can someone take a look? I'll commit the patch on Cesar's behalf if it'

Re: -fuse-caller-save - Collect register usage information

> This is the updated version of the previously approved patch > submitted here (http://gcc.gnu.org/ml/gcc-patches/2013-03/msg01320.html ). > The changes are: > - using a new hook call_fusage_contains_non_callee_clobbers, > - incorporating minor review comments from Richard Sandiford >( http://

Re: patch to fix PR60969

Hello! Attached patch enhances the testcase to also check for presence of MMX registers on all 32bit x86 targets. 2014-05-17 Uros Bizjak * g++.dg/pr60969.C: Compile for all ilp32 x86 targets. (dg-options): Add -mfpmath=387. (dg-final): Check that no MMX registers are used. Tested

[PATCH, doc]: Improve -free description

Hello! -free defaults to enabled also for Alpha. The option is also enabled for -Os on all targets. 2014-05-17 Uros Bizjak * doc/invoke.texi (free): Mention Alpha. Also enabled at -Os. Committed to 4.9 and mainline SVN. Uros. Index: invoke.texi

[PATCH, doc]: Fix a bunch of warnings in *.texi files

Hello! Attached patch fixes: md.texi:1057: warning: node next `Constraints' in menu `Asm Labels' and in sectioning `Size of an asm' differ extend.texi:7175: warning: node `Asm Labels' is next for `Size of an asm' in sectioning but not in menu extend.texi:7175: warning: node prev `Size of an asm'

[patch] libstdc++/60966 fix synchronisation in std::promise

This patch implements the correct synchronisation guarantees for promise::set_value() and promise:;set_exception, so that successful calls to those functions synchronize with functions that detect the ready state. Previously a waiting function could detect a ready state as soon as the result was

Re: [i386] Replace builtins with vector extensions

Ping On Mon, 28 Apr 2014, Marc Glisse wrote: Ping http://gcc.gnu.org/ml/gcc-patches/2014-04/msg00590.html (note that ARM seems to be doing the same thing for their neon intrinsics, see Ramana's patch series posted today) On Fri, 11 Apr 2014, Marc Glisse wrote: Hello, the previous discuss

[PATCH, libgomp doc]: Fix all libgomp.texi warnings

Hello! Attached patch fixes following libgomp.texi warnings: libgomp.texi:169: warning: multiple @menu libgomp.texi:184: warning: multiple @menu libgomp.texi:914: warning: node `omp_init_lock' is next for `omp_set_schedule' in sectioning but not in menu libgomp.texi:947: warning: node `omp_set_sc

Re: calloc = malloc + memset

Ping Jakub? https://gcc.gnu.org/ml/gcc-patches/2014-04/msg01104.html On Wed, 23 Apr 2014, Richard Biener wrote: On Fri, Apr 18, 2014 at 8:27 PM, Marc Glisse wrote: Thanks for the comments! On Fri, 18 Apr 2014, Jakub Jelinek wrote: The passes.def change makes me a little bit nervous, but i

Re: [Patch,Microblaze]: Added Break Handler Support

On 05/14/14 02:24, Ajit Kumar Agarwal wrote: Based on the Feedback, Resubmitting the Updated Patch. [Patch, MicroBlaze] Add break Handler Support Added Break Handler support to incorporate the hardware and software break. The Break Handler routine will be generating the rtbd instruction. At th

Re: [v3] Slightly improve operator new

Ping. On Tue, 15 Apr 2014, Marc Glisse wrote: Ping http://gcc.gnu.org/ml/gcc-patches/2014-03/msg00051.html On Sun, 2 Mar 2014, Marc Glisse wrote: Hello, inlining operator new (with LTO or otherwise), I noticed that it has a complicated implementation, which makes it hard to use this inlin

Re: [v3] Slightly improve operator new

On 17/05/14 18:30 +0200, Marc Glisse wrote: Ping. On Tue, 15 Apr 2014, Marc Glisse wrote: Ping http://gcc.gnu.org/ml/gcc-patches/2014-03/msg00051.html The patch is OK for trunk - sorry for forgetting about it.

[committed PATCH] Fix bad change in fortran/check.c

I have committed the following patch as obvious: Dominique Index: gcc/fortran/ChangeLog === --- gcc/fortran/ChangeLog (revision 210559) +++ gcc/fortran/ChangeLog (working copy) @@ -1,3 +1,8 @@ +2014-05-17 Dominique d'Hum

Re: [PATCH 4/5] add finalizers to ggc

On Tue, May 13, 2014 at 11:41:46AM +0200, Richard Biener wrote: > On Tue, May 13, 2014 at 8:41 AM, wrote: > > From: Trevor Saunders > > > > This implements finalizers by keeping a list of registered finalizers > > and after every mark but before sweeping check to see if any of them are > > for u

Re: [PATCH, doc]: Fix a bunch of warnings in *.texi files

My bad. My version of makeinfo wasn't reporting these errors. However, this isn't right either. There are two subsections that are now under "Size of an asm" that should be under "Variables in Specified Registers." How about this (attached)? dw On 5/17/2014 6:06 AM, Uros Bizjak wrote: He

Re: [fortran-dev] Merge the trunk into the branch

Dear Dominique, dear Tim, Dominique Dhumieres wrote: I have updated the trunk into the "fortran-dev" branch, ... Thanks. I had to apply the following patch in order to bootstrap: Thanks for fix for the merge fallout! That saved me to figure out why it didn't work. I changed the nested "if" i