<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 09/13/2017 06:53 AM, C Bergström
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAOnawYo8eCcyFjD1VbF9r77b86b5MGShiO1LoVU3prykB0Wt8g@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <div dir="ltr"><br>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Wed, Sep 13, 2017 at 7:43 PM, Hal
            Finkel <span dir="ltr"><<a moz-do-not-send="true"
                href="mailto:hfinkel@anl.gov" target="_blank">hfinkel@anl.gov</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div bgcolor="#FFFFFF" text="#000000"><span class="">
                  <p><br>
                  </p>
                  <div class="m_-268822120178151296moz-cite-prefix">On
                    09/13/2017 02:16 AM, C Bergström wrote:<br>
                  </div>
                  <blockquote type="cite">
                    <div dir="ltr">
                      <div>
                        <div>
                          <div>
                            <div>
                              <div>A completely non-technical point, but
                                what's the current "polly" license? Does
                                integrating that code conflict in any
                                way with the work being done to
                                relicense llvm?<br>
                              </div>
                            </div>
                          </div>
                        </div>
                      </div>
                    </div>
                  </blockquote>
                  <br>
                </span> Good question. I discussed this explicitly with
                Tobias, and his general feeling is that relicensing isl
                again would be doable if necessary (we already did this
                once, to an MIT license, in order to enable better LLVM
                integration).<span class=""><br>
                  <br>
                  <blockquote type="cite">
                    <div dir="ltr">
                      <div>
                        <div>
                          <div>
                            <div>
                              <div><br>
                              </div>
                              Does adding polly expose any additional
                              legal risks? Some people from Reservoir
                              labs have explicitly stated to me that
                              some of their patents target polyhedral
                              optimizations. You should almost certainly
                              review their portfolio or contact them.<br>
                              <br>
                            </div>
                            If at some point someone wants to add real
                            loop optimizations - will there be a
                            conflict?<br>
                          </div>
                        </div>
                      </div>
                    </div>
                  </blockquote>
                  <br>
                </span> Can you define "real loop optimizations"?<span
                  class=""><br>
                </span></div>
            </blockquote>
            <div><br>
            </div>
            <div>I think most readers here will understand what I mean.
              I can go find specific chapters of textbooks if it's
              unclear. Maybe the word "real" could be replaced with
              traditional, well tested, industry standard or something
              else. (ok I'll stop being snarky)<br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    That's what I thought you meant. No, I believe there's not a
    conflict. In fact, this will provide infrastructure to make this
    easier. While you can handle a bunch of these as one problem using
    this kind of framework, you don't need to do so.<br>
    <br>
    <blockquote
cite="mid:CAOnawYo8eCcyFjD1VbF9r77b86b5MGShiO1LoVU3prykB0Wt8g@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div>I really do appreciate your feedback and I do think
              something beyond just a soft discussion is required on the
              IP/license vetting. The relicense process used before
              should be substantially similar to the process which LLVM
              is going to use. There's a big difference between someone
              randomly changing a license header and nobody complaining
              vs getting explicit and signed agreements from all
              copyright holders.<br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    The LLVM Foundation has a good lawyer advising on the relicensing
    process. No one is taking this lightly.<br>
    <br>
    <blockquote
cite="mid:CAOnawYo8eCcyFjD1VbF9r77b86b5MGShiO1LoVU3prykB0Wt8g@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div>Further, my reading on some of the patents causes
              significant concerns. (A point everyone will want to
              ignore until it's too late). I'm avoiding exact
              references, but soon I'll start I'll start listing exact
              patents if nobody else cares.<br>
              <br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Please raise IP concerns with the LLVM Foundation board of directors
    (<a class="moz-txt-link-abbreviated" href="mailto:board@llvm.org">board@llvm.org</a>). We don't discuss specific IP issues on this list.<br>
    <br>
    Thanks again,<br>
    Hal<br>
    <br>
    <blockquote
cite="mid:CAOnawYo8eCcyFjD1VbF9r77b86b5MGShiO1LoVU3prykB0Wt8g@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div><br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Hal Finkel
Lead, Compiler Technology and Programming Languages
Leadership Computing Facility
Argonne National Laboratory</pre>
  </body>
</html>