# -*- text -*-
#
# Copyright (c) 2025-2026 Nanook Consulting  All rights reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
# This is the US/English general help file for PRTE's hwloc support.
#
[invalid binding_policy]

The specified %s policy is not recognized:

   Policy: %s

Please check for a typo or ensure that the option is a supported one.
#
[bad-processor-type]

The default CPU list contains an invalid modifier:

   Default CPU list:  %s
   Modifier:  %s

The modifier should indicate the type of CPU being used in the list —
the only valid values are HWTCPUS (for use of hwthreads as independent
CPUs) or CORECPUS (for use of cores as independent CPUs). Please
correct the input.
#
[unrecognized-modifier]

The binding request contains an unrecognized modifier:

   Request: %s

Please check your request and try again.
#
[bind-upwards]

Binding is performed to the first available specified object type
within the object where the process was mapped. In other words,
binding can only be done to the mapped object or to a resource located
beneath that object.

The specified binding lies above the mapping object type:

   Mapping level: %s
   Binding level: %s

Please correct the map/bind directives and try again.
#
[pu-not-found]
Construction of the binding output string failed due to inability
to obtain a processor unit object:

  PU number: %u

There will be no impact to your application, so we will continue
but will not be able to output the binding locations.
#
[unfound-cpu]
The CPU list provided on your cmd line contains at least one entry that
could not be resolved:

  CPU list:  %s
  Entry:     %s
  CPU type:  %s

Each entry must be a logical CPU index, or a "low-high" range of them.
The most common reason for a failure here is specifying the CPU list in
terms of HWTs while failing to request that we treat HWTs as independent
CPUs (which means we default to treating the CPU IDs as cores).
Please correct your input and try again.
