<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 7/3/20 3:42 PM, Itaru Kitayama via
      Openmp-dev wrote:<br>
    </div>
    <blockquote type="cite" cite="mid:CANW9uyvMHo55eOyMsgRH43=0e7xqwHWDpQmh6BGniZ2mAkC72w@mail.gmail.com">
      
      <div>
        <div dir="auto">Jeff,</div>
      </div>
      <div dir="auto">Linux supports other arches than X86, and the</div>
      <div dir="auto">layout of cpuinfo is different across the
        architectures.</div>
      <div dir="auto"><br>
      </div>
      <div dir="auto">In the runtime code if you take a look at already
         there are ifdefs.</div>
      <div dir="auto"><br>
      </div>
      <div dir="auto">Itaru.</div>
    </blockquote>
    <p><br>
    </p>
    <p>The alternative that you're proposing is to fork lscpu to read
      /proc/cpuinfo instead?</p>
    <p>We do understand that /proc/cpuinfo has architecture
      dependencies, and this is unfortunate in this context, but it is
      the interface that Linux provides. How does lscpu deal with those
      dependencies? Should our parser just be more robust?<br>
    </p>
    <p> -Hal<br>
    </p>
    <p><br>
    </p>
    <blockquote type="cite" cite="mid:CANW9uyvMHo55eOyMsgRH43=0e7xqwHWDpQmh6BGniZ2mAkC72w@mail.gmail.com">
      <div><br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Fri, Jul 3, 2020 at 23:48
            Jeff Hammond <<a href="mailto:jeff.science@gmail.com" moz-do-not-send="true">jeff.science@gmail.com</a>>
            wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">I’m not
            sure lscpu program is any better and it’s not standard on
            Linux the way /proc/cpuinfo is.<br>
            <br>
            What is the specific problem you are seeing? Perhaps you can
            explain that before trying to design a solution. <br>
            <br>
            Jeff<br>
            <br>
            > On Jul 2, 2020, at 10:55 PM, Itaru Kitayama via
            Openmp-dev <<a href="mailto:openmp-dev@lists.llvm.org" target="_blank" moz-do-not-send="true">openmp-dev@lists.llvm.org</a>>
            wrote:<br>
            > <br>
            > Is there a plan to move away from arch dependent
            cpuinfo file to lscup<br>
            > when creating an affinity map? It has clearly different
            a format on AArch64.<br>
            > _______________________________________________<br>
            > Openmp-dev mailing list<br>
            > <a href="mailto:Openmp-dev@lists.llvm.org" target="_blank" moz-do-not-send="true">Openmp-dev@lists.llvm.org</a><br>
            > <a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev" rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev</a><br>
          </blockquote>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
Openmp-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Openmp-dev@lists.llvm.org">Openmp-dev@lists.llvm.org</a>
<a class="moz-txt-link-freetext" href="https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev</a>
</pre>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Hal Finkel
Lead, Compiler Technology and Programming Languages
Leadership Computing Facility
Argonne National Laboratory</pre>
  </body>
</html>