<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Its awesome to see so much progress on this!</p>
    <p>A very minor question - why is it called M680x0 and not M68K
      given that's what the target arch/triple is and how its usually
      referred to?</p>
    <p>Sorry for the bikeshedding....</p>
    <p>Simon.<br>
    </p>
    <div class="moz-cite-prefix">On 30/09/2020 21:14, Min-Yih Hsu via
      llvm-dev wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAJyG1bPiBzk68E9Jct_eZtsqO5pNOSg3sacqSC-9BzT4fa1aRg@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Hi All,
        <div><br>
        </div>
        <div>I've composed a draft roadmap for this new target. I've
          decided to try Github's "Projects" feature, as it provides a
          clearer view to see all the blockers and action items, IMAO.
          Here is the link:</div>
        <div><a
            href="https://github.com/M680x0/M680x0-mono-repo/projects"
            moz-do-not-send="true">https://github.com/M680x0/M680x0-mono-repo/projects</a><br>
        </div>
        <div><br>
        </div>
        <div>Currently I only created two major milestones: Becoming an
          experimental target and becoming an official target. For each
          milestone, I've listed the expected features, estimated time
          frame (though I'm not really confident on that), and most
          importantly, the blockers for the milestone.</div>
        <div>Fortunately, all of our essential features are complete
          (e.g. ISel, MC), so there will be more house cleaning tasks
          and bug fixing than adding new features in the second
          milestone.</div>
        <div><br>
        </div>
        <div>In addition to the aforementioned two milestones, I've
          added "be able to run toy programs" as a separate milestone to
          accommodate some more urgent tasks right now. More
          specifically, driver problems that make Clang unable to
          leverage all our components.</div>
        <div><br>
        </div>
        <div>Thank you!</div>
        <div>Min</div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Tue, Sep 29, 2020 at 11:27
          AM Renato Golin <<a href="mailto:rengolin@gmail.com"
            moz-do-not-send="true">rengolin@gmail.com</a>> wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div dir="ltr">
            <div dir="ltr">On Tue, 29 Sep 2020 at 18:53, John Paul
              Adrian Glaubitz <<a
                href="mailto:glaubitz@physik.fu-berlin.de"
                target="_blank" moz-do-not-send="true">glaubitz@physik.fu-berlin.de</a>>
              wrote:<br>
            </div>
            <div class="gmail_quote">
              <blockquote class="gmail_quote" style="margin:0px 0px 0px
                0.8ex;border-left:1px solid
                rgb(204,204,204);padding-left:1ex">So, shall we setup a
                server for that or is there some existing infrastructure<br>
                from LLVM that is used in this case?<br>
              </blockquote>
              <div><br>
              </div>
              <div>Unfortunately, we don't have a centralised
                infrastructure like GCC. Each target community is
                responsible for maintaining their own buildbots.</div>
              <div><br>
              </div>
              <div>All we provide is the "build master", which
                aggregates all builds, email when there are regressions,
                etc.</div>
              <div><br>
              </div>
              <div><a href="http://llvm.org/docs/HowToAddABuilder.html"
                  target="_blank" moz-do-not-send="true">http://llvm.org/docs/HowToAddABuilder.html</a><br>
              </div>
              <div><br>
              </div>
              <div>It should be trivial to copy & paste an existing
                bot config and change to add the experimental hardware
                (once it's in the tree).</div>
              <div><br>
              </div>
              <div>Pay attention to the version of buildbot you install,
                as using an even slightly different version can cause
                weird errors.</div>
              <div><br>
              </div>
              <div>(I'm sure you understand how many times we tried to
                move on for the past 10 years... :)</div>
              <div><br>
              </div>
              <div><br>
              </div>
              <blockquote class="gmail_quote" style="margin:0px 0px 0px
                0.8ex;border-left:1px solid
                rgb(204,204,204);padding-left:1ex">As far as I
                understand, 90% of the tests already pass (according to
                Min).<br>
              </blockquote>
              <div><br>
              </div>
              <div>Awesome! We have buildbots with test-suite running,
                you can copy those, too. There were some QEMU bots in
                the past, I'm not sure they're around, but the infra to
                run them should still be there.</div>
              <div><br>
              </div>
              <div>cheers,</div>
              <div>--renato</div>
            </div>
          </div>
        </blockquote>
      </div>
      <br clear="all">
      <div><br>
      </div>
      -- <br>
      <div dir="ltr" class="gmail_signature">
        <div dir="ltr">
          <div>Min-Yih Hsu</div>
          <div>Ph.D Student in ICS Department, University of California,
            Irvine (UCI).<br>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
cfe-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a>
<a class="moz-txt-link-freetext" href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a>
</pre>
    </blockquote>
  </body>
</html>