On 04/19/2011 09:14 AM, Richard Sandiford wrote:
Tested on x86_64-linux-gnu and arm-linux-gnueabi. OK to install?
OK with me. Thanks for your patience. Just a couple of minor nits below
+ extern const int internal_fn_flags_array[];
+ return internal_fn_flags_array[(int) fn];
+}
+
+exte
On Tue, Apr 19, 2011 at 3:14 PM, Richard Sandiford
wrote:
> Richard Guenther writes:
>>> We really should be able to treat calls to pure internal functions
>>> like calls to pure "real" functions though.
>>>
>>> TBH, I think this is an example of why trying to so hard to avoid a tree
>>> code for
Richard Guenther writes:
>> We really should be able to treat calls to pure internal functions
>> like calls to pure "real" functions though.
>>
>> TBH, I think this is an example of why trying to so hard to avoid a tree
>> code for the internal function is working against us. Most of the patch
>
On Mon, Apr 18, 2011 at 3:37 PM, Richard Sandiford
wrote:
> Richard Guenther writes:
>>> +/* Expand a call to internal function FN. ARGS is an array of the
>>> + function's arguments and LHS is where the result should be stored. */
>>> +
>>> +void
>>> +expand_internal_call (enum internal_fn f
Richard Guenther writes:
>> +/* Expand a call to internal function FN. ARGS is an array of the
>> + function's arguments and LHS is where the result should be stored. */
>> +
>> +void
>> +expand_internal_call (enum internal_fn fn, tree lhs, tree *args)
>> +{
>> + internal_fn_expanders[(int) f
On Mon, Apr 18, 2011 at 11:26 AM, Richard Sandiford
wrote:
> Diego Novillo writes:
>> On Thu, Apr 14, 2011 at 09:43, Richard Sandiford
>> wrote:
>>> +/* This file specifies a list of internal "functions". These functions
>>> + differ from built-in functions in that they have no linkage and ca
Diego Novillo writes:
> On Thu, Apr 14, 2011 at 09:43, Richard Sandiford
> wrote:
>> +/* This file specifies a list of internal "functions". These functions
>> + differ from built-in functions in that they have no linkage and cannot
>> + be called directly by the user. They represent operat
On Thu, Apr 14, 2011 at 09:43, Richard Sandiford
wrote:
> +/* This file specifies a list of internal "functions". These functions
> + differ from built-in functions in that they have no linkage and cannot
> + be called directly by the user. They represent operations that are only
> + synt
Richard Sandiford writes:
> I'm implementing the multi-vector load/store support described here:
>
> http://gcc.gnu.org/ml/gcc/2011-03/msg00322.html
>
> For the purposes of this message, the main thing is that the losds
> and stores are more naturally represented as GIMPLE_CALLs rather
> than
