On Thu, Oct 22, 2015 at 02:51:34PM +0200, Tom de Vries wrote:
> On 22/10/15 14:27, Jakub Jelinek wrote:
> >The state before the patch is:
> >1) the omp_fn children created during the pre-SSA ompexp pass are dumped
> >first in the *.ssa dump and in all the following ones (these are created
> >
On 22/10/15 14:27, Jakub Jelinek wrote:
The state before the patch is:
1) the omp_fn children created during the pre-SSA ompexp pass are dumped
first in the *.ssa dump and in all the following ones (these are created
as low gimple, non-SSA)
Hi,
I do see those child fns before the ssa d
On Thu, Jun 04, 2015 at 05:02:42PM +0200, Tom de Vries wrote:
> >So why does add_new_function not do the dumping and to the correct
> >place? That is,
> >you are dumping things twice here, once in omp expansion and then again when
> >the
> >new function reaches omp expansion?
> >
>
> Dumping twi
;>>> where we split off a new high gimple function.
>>>>
>>>> And in expand_omp_taskreg and expand_omp_target, where we split off a
>>>> new low
>>>> gimple function, we now dump the new function into the current (ompexp)
>>&g
and what kind of function is
created.
Bootstrapped and reg-tested on x86_64.
OK for trunk ?
Thanks,
- Tom
commit b925b393c3d975a9281789d97aff8a91a8b53be0
Author: Thomas Schwinge
Date: Sun Mar 1 15:05:15 2015 +0100
Don't dump low gimple functions in gimple dump
id:"
statement at the start of
>> cgraph_add_new_function to give a better idea when and what kind of function
>> is
>> created.
>>
>> Bootstrapped and reg-tested on x86_64.
>>
>> OK for trunk ?
>>
>> Thanks,
>> - Tom
>
> commit b925b393
inally, we dump an information statement at the start of
> cgraph_add_new_function to give a better idea when and what kind of function
> is
> created.
>
> Bootstrapped and reg-tested on x86_64.
>
> OK for trunk ?
>
> Thanks,
> - Tom
commit b925b393c3d975a9281789
Honza,
Consider this program:
...
int
main(void)
{
#pragma omp parallel
{
extern void foo(void);
foo ();
}
return 0;
}
...
When compiling this program with -fopenmp, the ompexp pass splits off a new
function called main._omp_fn.0 containing the call to foo. The new function is
then
