Hi!
On Fri, 9 Jan 2015 16:37:00 +0100, Tom de Vries wrote:
> For the oacc kernels patch series I need a fortran builtin with fn spec
> attribute (as mentioned here:
> https://gcc.gnu.org/ml/gcc/2014-12/msg1.html ).
>
> Attached patch adds a function gfc_define_builtin_with_spec that allows
>> If unused on trunk, why would we commit it there?
>> When your branch is merged, you'll merge it along. Otherwise that defeats
>> the purpose of working on a branch, unless I misunderstand something...
>
> This patch is not branch-specific.
As far as I understand, we don’t add unused code to
On 09-01-15 18:11, FX wrote:
If unused on trunk, why would we commit it there?
When your branch is merged, you'll merge it along. Otherwise that defeats the
purpose of working on a branch, unless I misunderstand something...
This patch is not branch-specific.
Thanks,
- Tom
FX
Le 9 janv
If unused on trunk, why would we commit it there?
When your branch is merged, you'll merge it along. Otherwise that defeats the
purpose of working on a branch, unless I misunderstand something...
FX
> Le 9 janv. 2015 à 16:37, Tom de Vries a écrit :
>
> Jakub,
>
> For the oacc kernels patch
Jakub,
For the oacc kernels patch series I need a fortran builtin with fn spec
attribute (as mentioned here: https://gcc.gnu.org/ml/gcc/2014-12/msg1.html ).
Attached patch adds a function gfc_define_builtin_with_spec that allows me to
define such a builtin.
At this point there's no user
