Question regarding bug 70584

While analysing this bug we arrived to the following code at tree.c:145 (lvalue_kind): case VAR_DECL: if (TREE_READONLY (ref) && ! TREE_STATIC (ref) && DECL_LANG_SPECIFIC (ref) && DECL_IN_AGGR_P (ref)) return clk_none; That condition fails so a fall-through to the next

Re: [PING][PATCH] New plugin event when evaluating a constexpr call

Hi I made the corrections to the patch. Changelog 2016-5-6 Andres Tiraboschi <andres.tirabos...@tallertechnologies.com> *gcc/plugin.c (PLUGIN_EVAL_CALL_CONSTEXPR): New event. *gcc/plugin.def (PLUGIN_EVAL_CALL_CONSTEXPR): New event. *gcc/cp/constexpr.c (constexpr_fundef):

Re: [PING][PATCH] New plugin event when evaluating a constexpr call

Hi, thanks for the feedback, I'll do the changes. 2016-05-04 13:16 GMT-03:00 Jason Merrill <ja...@redhat.com>: > On 05/02/2016 03:28 PM, Andres Tiraboschi wrote: >> >> + constexpr_call_info call_info; >> + call_info.function = t; >> + call_info.call_stack

Re: [PING][PATCH] New plugin event when evaluating a constexpr call

2016-04-26 10:41 GMT-03:00 Andres Tiraboschi <andres.tirabos...@tallertechnologies.com>: > Hi, thanks for answering, > > 2016-04-25 16:21 GMT-03:00 Jason Merrill <ja...@redhat.com>: >> Let's create a constexpr.h rather than expose constexpr internals to all of >> t

Re: [PING][PATCH] New plugin event when evaluating a constexpr call

Hi, thanks for answering, 2016-04-25 16:21 GMT-03:00 Jason Merrill : > Let's create a constexpr.h rather than expose constexpr internals to all of > the front end. Really, I'd prefer to avoid exposing them at all. Why does > what you want to do require all this implementation

[PING][PATCH] New plugin event when evaluating a constexpr call

Hi This patch adds a plugin event when evaluating a call expression in constexpr. The goal of this patch is to allow the plugins to analyze and or modify the evaluation of constant expressions. Changelog 2016-4-25 Andres Tiraboschi <andres.tirabos...@tallertechnologies.com> *gcc/pl

Re: [PATCH] New flag in order to dump information about template instantiations.

2016-03-29 12:07 GMT-03:00 Andres Tiraboschi <andres.tirabos...@tallertechnologies.com>: > Hi, > the attached patch adds a new compilation flag > 'ftemplate-instantiations' in order > to allow dumping debug information for template instantiations. > This flag has 2 possible va

[PATCH] New plugin event when evaluating a constexpr call

Hi This patch adds a plugin event when evaluating a call expression in constexpr. The goal of this patch is to allow the plugins to analyze and or modify the evaluation of constant expressions. Changelog 2016-3-30 Andres Tiraboschi <andres.tirabos...@tallertechnologies.com> *gcc/pl

[PATCH] New flag in order to dump information about template instantiations.

add_template_instantiations_callbacks in order to access information about witch template instantiations had been made. Changelog 2016-03-29 Andres Tiraboschi <andres.tirabos...@tallertechnologies.com> * gcc/c-family/c.opt (ftemplate-instantiations): New flag. * gcc/flag-types.h (ti_dump_options): Ne

Re: [PATCH] New flag for dumping information about constexpr function calls memoization (GCC 5.2.0)

2016-01-28 17:54 GMT-03:00 Joseph Myers : > Any patch adding a new option needs to add documentation for it to > invoke.texi (both substantive documentation, and inclusion in the summary > lists of options). > > -- > Joseph S. Myers > jos...@codesourcery.com Hi, Thanks

[PATCH] New flag for dumping information about constexpr function calls memoization (GCC 5.2.0)

Hi, This patch adds a flag (-fdump-memoization-hits) in order to dump information about wich constexpr functions calls are memoized. This is patch is for gcc-5.2.0. If OK, please commit it for me since I don't have write access. patch: diff --git a/gcc/common.opt b/gcc/common.opt index

[PATCH] New plugin events when evaluating constexpr expressions.

Hi This patch adds two plugins events when evaluated call expression and an init or modify expression in constexpr. The goal of this patch is to allow the plugins to analyze and or modify the evaluation of constant expressions. This patch also adds an event that is called when the parsing of

[PATCH] Optional escaped commas in macros

This patch is for gcc-5.2.0 adds the XXX option to the preprocessor that enables to escape commas when passing macro arguments. This feature is useful in C++ when the macro argument is a template with more than one argument, and adding extra ( ) is not possible, as shown in this example:

Re: [PATCH] Optional escaped commas in macros

2015-10-27 16:35 GMT-03:00 Andres Tiraboschi <andres.tirabos...@tallertechnologies.com>: > This patch is for gcc-5.2.0 adds the XXX option to the preprocessor Sorry I forgot to clarify that fmacro-escaped-commas is the option name. Thanks, Andrés.

[PATCH] Fix 67064 - Register asm variable broken

Hi, this patch fix the following bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67064 for gcc 5.2 It passes all the gcc tests except for this: FAIL: g++.dg/cpp1y/auto-fn15.C -std=gnu++14 (test for excess errors) but this also happens without the patch. This patch was implemented for gcc 5.2

Re: [PATCH] Adding warning for constexpr's

. 2015-06-12 18:35 GMT-03:00 Joseph Myers jos...@codesourcery.com: On Fri, 12 Jun 2015, Andres Tiraboschi wrote: Hi, this patch is for adding a warning when a constexpr cannot be evaluated at compile time. This is a single case: type var = fun(args...), with fun declared as a constexpr. All

Re: [PATCH] Adding warning for constexpr's

2015-06-12 18:35 GMT-03:00 Joseph Myers jos...@codesourcery.com: On Fri, 12 Jun 2015, Andres Tiraboschi wrote: Hi, this patch is for adding a warning when a constexpr cannot be evaluated at compile time. This is a single case: type var = fun(args...), with fun declared as a constexpr. All

[PATCH] Adding warning for constexpr's

Hi, this patch is for adding a warning when a constexpr cannot be evaluated at compile time. This is a single case: type var = fun(args...), with fun declared as a constexpr. diff --git a/gcc/common.opt b/gcc/common.opt index b49ac46..88374b1 100644 --- a/gcc/common.opt +++ b/gcc/common.opt @@

Re: [PATCH] plugin event for C/C++ function definitions

2015-05-18 16:51 GMT-03:00 andres.tirabos...@tallertechnologies.com: Hi, this patch adds two new plugin events PLUGIN_START_PARSE_FUNCTION and PLUGIN_FINISH_PARSE_FUNCTION. These events are invoked at start_function and finish_function in gcc/c/c-decl.c and gcc/cp/decl.c respectively in the

[PATCH] plugin event for C/C++ function definitions

Hi, this patch adds two new plugin events PLUGIN_START_PARSE_FUNCTION and PLUGIN_FINISH_PARSE_FUNCTION. These events are invoked at start_function and finish_function in gcc/c/c-decl.c and gcc/cp/decl.c respectively in the C and C++ frontends. PLUGIN_START_PARSE_FUNCTION is called before

Re: [PING][PATCH V2] plugin event for C/C++ function definitions

PING, request for maintainer please 2014-12-02 15:15 GMT-03:00 Andres Tiraboschi andres.tirabos...@tallertechnologies.com: Hi, this patch adds a new plugin event PLUGIN_START_PARSE_FUNCTION and PLUGIN_FINISH_PARSE_FUNCTION that are invoked at start_function and finish_function respectively

[PING][PATCH V2] plugin event for C/C++ function definitions

Hi, this patch adds a new plugin event PLUGIN_START_PARSE_FUNCTION and PLUGIN_FINISH_PARSE_FUNCTION that are invoked at start_function and finish_function respectively in the C and C++ frontends. PLUGIN_START_PARSE_FUNCTION is called before parsing the function body.

Re: [PATCH V2] plugin event for C/C++ function definitions

I forgot to mention that i have no write privileges, please commit this for me if it's OK

Re: [PATCH] plugin event for C/C++ function definitions

2014-11-14 7:08 GMT-03:00 Richard Biener richard.guent...@gmail.com: On Thu, Nov 13, 2014 at 6:42 PM, Andres Tiraboschi andres.tirabos...@tallertechnologies.com wrote: Hi, this patch adds a new plugin event PLUGIN_START_FUNCTION and PLUGIN_FINISH_FUNCTION that are invoked at start_function

[PATCH V2] plugin event for C/C++ function definitions

Hi, this patch adds a new plugin event PLUGIN_START_PARSE_FUNCTION and PLUGIN_FINISH_PARSE_FUNCTION that are invoked at start_function and finish_function respectively in the C and C++ frontends. PLUGIN_START_PARSE_FUNCTION is called before parsing the function body.

[PATCH] plugin event for C/C++ function definitions

Hi, this patch adds a new plugin event PLUGIN_START_FUNCTION and PLUGIN_FINISH_FUNCTION that are invoked at start_function and finish_function respectively in the C and C++ frontends. PLUGIN_START_FUNCTION is called before parsing the function body. PLUGIN_FINISH_FUNCTION is called after