This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [gomp] Challenges in Implementing OpenMP


 Btw. I also think GENERIC is the place to start handling stuff like this, some things about semantics have to be done in the frontend but the heavy stuff has to be done in GENERIC and from there on .

 / Lars Segerlund.

On Thu, 14 Oct 2004 12:59:45 +0200
"Giovanni Bajo" <giovannibajo@libero.it> wrote:

> Paolo Bonzini wrote:
> 
> >> Essentially, OpenMP restructures the original code. The above
> >> example is incredibly simple, and only touches the surface of
> >> OpenMP's complexities.
> >
> > But it also highlights a strength of GCC: support for nested functions
> > means that we get escape analysis for free.
> 
> Yes, that was also my idea. With nested function, you get also variable sharing
> for free, while you still have to handle private variables somehow (you can
> mark some local variables as private of the thread, that is each thread has its
> own version): a way could be to pass them as arguments to the nested function.
> 
> But stilll, I cannot see why this could not be handled at GENERIC level,
> instead of being done in the frontend.
> 
> Giovanni Bajo
> 
> 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]