This is the mail archive of the
mailing list for the GCC project.
Re: About adding OMPT into GNU's libgomp
- From: Harald Servat <redcrash at gmail dot com>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: gcc at gcc dot gnu dot org, khuck at cs dot uoregon dot edu
- Date: Tue, 14 Apr 2015 09:56:37 +0200
- Subject: Re: About adding OMPT into GNU's libgomp
- Authentication-results: sourceware.org; auth=none
- References: <CAEOTYRe1iUojad7a-sTQJBAZiguS==dVjryfb_QVyB1Fwtobuw at mail dot gmail dot com> <20150413105327 dot GL1735 at tucnak dot redhat dot com>
2015-04-13 12:53 GMT+02:00 Jakub Jelinek <firstname.lastname@example.org>:
> The only thing I'd like to say is that it would be nice if the changes
> didn't affect performance of non-analyzed/traced apps, so if changes to hot
> code paths are needed, they should be done with care, guarded with
> __builtin_expect and benchmarked that they don't slow normal OpenMP code
> paths significantly.
The OMPT's phisolosophy is to limit as much as possible its
overhead. Still, we'll follow your indications in order to keep the
overhead as low as possible.
>> If there's nobody working on that, how should we start? According to
>> the GCC webpage, GCC 5 is open for regression and doc fixes only ,
>> so it could considered mature enough to be a starting point? Or should
>> we start in GCC 4.9.x? That being said, I've seen that there's a copy
>> of GCC in GitHub ; should we clone it, branch to GCC 5 (if that
>> exists), and then work on a local branch until we can send you some
>> patches? Or do you suggest a different work plan?
> Please see what Jonathan wrote. You really should start working on a branch
> from the trunk, and work towards incorporating it into the trunk (stage1
> of GCC 6, where the trunk is open for new features, closes usually in
Thank you very much.
"People say nothing is impossible, but I do nothing everyday."
- A. A. Milne