This is the mail archive of the 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: [libgomp, nvptx] Disable OMP_{DISPLAY_AFFINITY,AFFINITY_FORMAT} support


On Wed, 12 Dec 2018 10:36:17 +0100, Jakub Jelinek <> wrote:
> On Wed, Dec 12, 2018 at 09:29:36AM +0100, Tom de Vries wrote:
> > > This is the libgomp/ except libgomp/testsuite/ part of the gomp-5_0-branch
> > > merge to trunk I've just committed.

> > [libgomp, nvptx] Disable OMP_{DISPLAY_AFFINITY,AFFINITY_FORMAT} support

Thanks, Tom, for looking into these issues.  I'd also noticed these, but
not yet been able to allocate time to resolve them.  I'll test your
patches, too.

> Eventually we need to find a way how to transfer some ICVs and other data
> from the host to the offloading library, either process shared that aren't
> changing, which can include the hostname, getpid, or some others that would
> need to be passed for every target region.

That would probably also include any state that the respective language
runtime libraries maintain?  For example, C's global rounding mode as set
my "fesetround".  ..., and I now wonder how to propagate that from the
host libc to the target libcs, for example host: glibc vs. nvptx
offloading: newlib -- have to do a host-side "fegetround" before each
offloaded code region, or at least when there's been an intermediate
host-side "fesetround" call (so have to track these?), and likewise for
any other such state-changing functions?  Also, the "options" array and
call of "_gfortran_set_options" that the Fortran front end synthesizes
into each "main" function?

I have not yet looked into these things in detail, however.


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