This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH] GOMP_CPU_AFFINITY fails with >1024 cores
- From: Maxim Kuvyrkov <maxim at kugelworks dot com>
- To: Daniel J Blueman <daniel at numascale dot com>
- Cc: gcc-patches at gcc dot gnu dot org, gcc at gcc dot gnu dot org, Jakub Jelinek <jakub at redhat dot com>, Steffen Persvold <sp at numascale dot com>
- Date: Wed, 17 Jul 2013 17:27:16 +1200
- Subject: Re: [PATCH] GOMP_CPU_AFFINITY fails with >1024 cores
- References: <51E558B4 dot 5030100 at numascale dot com>
On 17/07/2013, at 2:29 AM, Daniel J Blueman wrote:
> Jakub et al,
> Steffen has developed a nice fix  for GOMP_CPU_AFFINITY failing with >1024 cores.
> What steps are needed to get this into GCC 4.8.2?
>  http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57298
<ironic>It's easy! Just follow the steps:</ironic>
1. You test the patch on one of the primary architectures and make sure there are no regressions in the testsuites.
2. Ideally you add a test that fails before your patch, but passes with it.
3. You post your final patch to gcc-patches@ mailing list (this is gcc@ mailing list); CC one of the maintainers. If you CC both -- each will think that the other will review the patch.
4. You include full description and analysis of the problem in the body of message (people are lazy to click on links). You describe how your patch fixes the problem. You write how and which architectures your patch was tested on.
5. You ping your submission every 2 weeks to one of the maintainers until they review your patch.