Re: [gomp 4.0] Handle OMP_DISPLAY_ENV

2013-03-19 Thread Jakub Jelinek
On Tue, Mar 19, 2013 at 07:05:12PM +0100, Tobias Burnus wrote: > I assume, you will create the gomp-4_0-branch when gcc.gnu.org is > fully operational. Additionally, I presume, the change-log > information should go to the file ChangeLog.gomp and not to > ChangeLog. Yes and yes. > 2013-03-19 Tob

Re: [gomp 4.0] Handle OMP_DISPLAY_ENV

2013-03-19 Thread Tobias Burnus
Jakub Jelinek wrote: +#include +#include /* For PRIu64. */ stdio.h is fine, but inttypes.h needs to be #ifdef HAVE_INTTYPES_H # include #endif for portability (libgomp/configure already checks for that). Good point. Attached the updated patch. I assume, you will create the gomp-4_0-b

Re: [gomp 4.0] Handle OMP_DISPLAY_ENV

2013-03-19 Thread Jakub Jelinek
On Tue, Mar 19, 2013 at 04:24:04PM +0100, Tobias Burnus wrote: > 2013-03-19 Tobias Burnus > > * env.c (handle_omp_display_env): New function. > (initialize_env): Use it. > > diff --git a/libgomp/env.c b/libgomp/env.c > index 65cbba8..e228bd9 100644 > --- a/libgomp/env.c > +++ b/lib

[gomp 4.0] Handle OMP_DISPLAY_ENV

2013-03-19 Thread Tobias Burnus
Attached is a first shot for OMP_DISPLAY_ENV. One could think about how to handle GOMP_CPU_AFFINITY and OMP_WAIT_POLICY. I currently print an empty list for affinity (although using GOMP_CPU_AFFINITY='' leads to a warning that the list is empty) and for OMP_WAIT_POLICY, an unset variable is han