On Fri, 1 Nov 2013, Jason Merrill wrote:
On 11/01/2013 11:13 AM, Marc Glisse wrote:
position). I can make it not call value_dependent_expression_p with a
null argument, but it seems more general to let
value_dependent_expression_p handle 0 like a number of other functions
already do.
OK. But
On 11/01/2013 11:13 AM, Marc Glisse wrote:
position). I can make it not call value_dependent_expression_p with a
null argument, but it seems more general to let
value_dependent_expression_p handle 0 like a number of other functions
already do.
OK. But the change is to type_..., not value_...,
On Fri, 1 Nov 2013, Jason Merrill wrote:
On 10/31/2013 07:03 PM, Marc Glisse wrote:
* pt.c (value_dependent_expression_p): Handle null argument.
What is calling this with a null argument? The recursive call near the end
of the function checks for null there.
See http://gcc.gnu.org/bu
On 10/31/2013 07:03 PM, Marc Glisse wrote:
* pt.c (value_dependent_expression_p): Handle null argument.
What is calling this with a null argument? The recursive call near the
end of the function checks for null there.
Jason
Hello,
__builtin_shuffle with 2 arguments is represented as having 3 arguments,
the second being 0, which isn't supported here.
Bootstrap+testsuite on x86_64-unknown-linux-gnu.
2013-11-01 Marc Glisse
PR c++/58834
gcc/cp/
* pt.c (value_dependent_expression_p): Handle null a
