> On x86_64, when the expected size of memcpy/memset is known (e.g, with
> FDO), libcall strategy is used with the size is > 8192. This value is
> hard coded, which makes it hard to do performance tuning. This patch
> adds two new parameters to do that. Potential usage includes
> per-application li
Hi Martin,
I have applied the patch on top of r201441 and I still get the warning for
gcc/testsuite/gfortran.dg/class_48.f90 with -m32 -O(2|s):
/opt/gcc/work/gcc/testsuite/gfortran.dg/class_48.f90: In function
'__final_test2_T.2136.constprop.0':
/opt/gcc/work/gcc/testsuite/gfortran.dg/class_48.f
---
gcc/cp/lambda.c | 77 ++---
1 file changed, 57 insertions(+), 20 deletions(-)
diff --git a/gcc/cp/lambda.c b/gcc/cp/lambda.c
index 98a7925..cf662bb 100644
--- a/gcc/cp/lambda.c
+++ b/gcc/cp/lambda.c
@@ -759,12 +759,9 @@ maybe_add_lambda_conv
---
gcc/cp/cp-tree.h | 2 +-
gcc/cp/decl.c| 3 ++-
gcc/cp/lambda.c | 2 +-
gcc/cp/parser.c | 6 ++
gcc/cp/pt.c | 4 ++--
5 files changed, 8 insertions(+), 9 deletions(-)
diff --git a/gcc/cp/cp-tree.h b/gcc/cp/cp-tree.h
index 64ff4e3..17bb8b9 100644
--- a/gcc/cp/cp-tree.h
+++ b/gcc/
---
gcc/cp/pt.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/gcc/cp/pt.c b/gcc/cp/pt.c
index dea1ec0..6e209f8 100644
--- a/gcc/cp/pt.c
+++ b/gcc/cp/pt.c
@@ -21317,8 +21317,15 @@ add_implicit_template_parms (size_t count, tree
parameters)
// Rewrite the
Hi Jason,
I've addressed your review comments and provided support for
conversion to function pointer for generic lambdas. I've sent the
patches as updates to the previous set. I'll wait for any further
comments before formalizing them into a cleaner set.
The changes now support the examples gi
---
gcc/cp/pt.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/gcc/cp/pt.c b/gcc/cp/pt.c
index a7baaba..99bc71b 100644
--- a/gcc/cp/pt.c
+++ b/gcc/cp/pt.c
@@ -1986,7 +1986,7 @@ determine_specialization (tree template_id,
tree decl_arg_types;
/* This
On Thu, Aug 1, 2013 at 7:25 AM, Adam Butcher wrote:
> ---
> gcc/cp/pt.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/gcc/cp/pt.c b/gcc/cp/pt.c
> index a7baaba..99bc71b 100644
> --- a/gcc/cp/pt.c
> +++ b/gcc/cp/pt.c
> @@ -1986,7 +1986,7 @@ determine_specialization
On Thu, Aug 1, 2013 at 7:25 AM, Adam Butcher wrote:
> ---
> gcc/cp/cp-tree.h | 2 +-
> gcc/cp/decl.c| 3 ++-
> gcc/cp/lambda.c | 2 +-
> gcc/cp/parser.c | 6 ++
> gcc/cp/pt.c | 4 ++--
> 5 files changed, 8 insertions(+), 9 deletions(-)
When submitting patches, you also need to add
On 03.08.2013 14:39, Gabriel Dos Reis wrote:
On Thu, Aug 1, 2013 at 7:25 AM, Adam Butcher
wrote:
---
gcc/cp/cp-tree.h | 2 +-
gcc/cp/decl.c| 3 ++-
gcc/cp/lambda.c | 2 +-
gcc/cp/parser.c | 6 ++
gcc/cp/pt.c | 4 ++--
5 files changed, 8 insertions(+), 9 deletions(-)
When submi
On 03.08.2013 14:35, Gabriel Dos Reis wrote:
On Thu, Aug 1, 2013 at 7:25 AM, Adam Butcher
wrote:
---
gcc/cp/pt.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/gcc/cp/pt.c b/gcc/cp/pt.c
index a7baaba..99bc71b 100644
--- a/gcc/cp/pt.c
+++ b/gcc/cp/pt.c
@@ -1986,7 +198
In the fix for PR57993, I missed some cases where the candidate table
needed to be updated when a candidate statement in the table might
become stale. This corrects those issues. One of the missing cases
showed up in povray when compiling SPEC cpu2006.
Bootstrapped and tested on powerpc64-unknow
On Sat, Aug 3, 2013 at 1:06 AM, Jan Hubicka wrote:
>> On x86_64, when the expected size of memcpy/memset is known (e.g, with
>> FDO), libcall strategy is used with the size is > 8192. This value is
>> hard coded, which makes it hard to do performance tuning. This patch
>> adds two new parameters t
Hi all,
the attached patch plugs a memory leak of the TRANSFER intrinsic,
which can occur when transferring to CHARACTER strings. For details
see the PR.
Regtested on x86_64-unknown-linux-gnu. Ok for trunk/4.8/4.7?
Cheers,
Janus
2013-08-03 Janus Weil
PR fortran/58058
* trans-intrin
On 08/01/2013 08:25 AM, Adam Butcher wrote:
+= DECL_TEMPLATE_INFO (callop)
+&& DECL_TEMPLATE_RESULT (DECL_TI_TEMPLATE (callop)) == callop;
An expression broken across lines should be parenthesized.
And let's move the building of 'call' for the non-template case up to be
with the templ
On 08/01/2013 02:06 PM, Marek Polacek wrote:
SAVE_EXPRs are evaluated only once;
in that COMPOUND_EXPR, when we first encounter SAVE_EXPR and
call get_initialized_tmp_var, we get temporary value for it, x.2.
Then, in the second part of the COMPOUND_EXPR, we meet SAVE_EXPR
again, but it already
Hello world,
the rather self-explanatory patch implements the -Wzerotrip
option. The positive form is not really useful, because
the option is on by default (so the default behavior is
not changed).
The negative form of the option, -Wno-zerotrip, suppresses the
warning. I have also added infor
This patch introduced new C++ testsuite regressions.
FAIL: g++.dg/ipa/devirt-11.C -std=gnu++98 scan-ipa-dump-times inline
"Discovered a virtual call to a known target" 3
FAIL: g++.dg/ipa/devirt-11.C -std=gnu++98 scan-ipa-dump-times inline
"and turned into root of the clone tree" 1
FAIL: g++.dg/i
On 08/02/2013 02:38 PM, David Malcolm wrote:
> OK for trunk? (as part of patches 3-6)
Ok.
Hi Maintainers,
This patch adds macros to support gprof in Aarch64. The difference
from the previous patch is that the compiler, while generating
"mcount" routine for an instrumented function, also passes the return
address as argument.
The "mcount" routine in glibc will be modified as follows.
On 08/02/2013 02:43 PM, David Malcolm wrote:
> gcc/
> * Makefile.in (GTFILES): Add context.h.
> * context.c (gcc::context::operator new): New.
> (gcc::context::gt_ggc_mx): New.
> (gcc::context::gt_pch_nx): New.
> (gcc::context::gt_pch_nx): New.
> * context.h (gcc
.. I don't know if at this Stage we are paying attention to these minor
details, but at least Patch 1 and 3 appear to have some overlong lines.
Thanks!
Paolo.
On 08/02/2013 02:48 PM, David Malcolm wrote:
> +pass_manager::gt_ggc_mx ()
> +{
> + ::gt_ggc_mx (all_passes);
> + ::gt_ggc_mx (all_small_ipa_passes);
> + ::gt_ggc_mx (all_lowering_passes);
> + ::gt_ggc_mx (all_regular_ipa_passes);
> + ::gt_ggc_mx (all_lto_gen_passes);
> + ::gt_ggc_mx (all_lat
This is the first in a series of cleanup patches to the pretty printer
data structures and routines.
Tested on an x86_64-suse-linux.
Applied to trunk.
2013-08-03 Gabriel Dos Reis
* pretty-print.h (pp_underscore): New.
(pp_comma): Tidy.
* gimple-pretty-print.c (dump_un
Hi, GCC/i386 currently has about 73 boolean parameters/knobs (defined
in ix86_tune_features[], indexed by ix86_tune_indices) to perform
micro-arch specific performance tuning. However such settings are hard
coded (fixed with a given -mtune setting) and is very hard to do
performance experiment.
Th
DR 1430 seems to be being resolved to prohibit passing a pack expansion
to a non-pack parameter of an alias template. I disagree with this
direction, but I'm going to go ahead and implement it for now.
The second patch implements DR 1286, which allows an alias template to
be equivalent to ano
On Sat, Aug 3, 2013 at 3:31 PM, Jason Merrill wrote:
> DR 1430 seems to be being resolved to prohibit passing a pack expansion to a
> non-pack parameter of an alias template. I disagree with this direction,
> but I'm going to go ahead and implement it for now.
I too disagree. Do we need a NB-le
On Fri, Aug 2, 2013 at 9:33 PM, Paolo Carlini wrote:
> If nobody has further comments over the next day or so, patch is Ok with me.
Committed. // http://gcc.gnu.org/ml/gcc-cvs/2013-07/msg00826.html
> PS: I think it would be nice if from to time you could provide a rough
> estimate of the amount
On 08/03/2013 06:43 PM, Gabriel Dos Reis wrote:
On Sat, Aug 3, 2013 at 3:31 PM, Jason Merrill wrote:
DR 1430 seems to be being resolved to prohibit passing a pack expansion to a
non-pack parameter of an alias template. I disagree with this direction,
but I'm going to go ahead and implement it
Hi,
>What's the format I should use? An email? Comments in the code? A PDF
>document? Or?
All sorts of comments in the code are always welcome: blurbs at the beginning
of each file explaining the main design choices, then smaller comments
explaining tricky points, TODO or FIXME when appropria
30 matches
Mail list logo
