
<html>

  <head>

    <meta content="text/html; charset=ISO-8859-1"

      http-equiv="Content-Type">

  </head>

  <body bgcolor="#FFFFFF" text="#000000">

    <div class="moz-cite-prefix">On 12/10/13 4:43 PM, Reid Kleckner

      wrote:<br>

    </div>

    <blockquote

cite="mid:CACs=tyLNYUxdZQPe_8Sm-np+0PXMvmFasBFp1g6pvu3QeyHnGw@mail.gmail.com"

      type="cite">

      <div dir="ltr">

        <div class="gmail_extra">

          <div class="gmail_quote">On Tue, Dec 10, 2013 at 4:31 PM,

            Quentin Colombet <span dir="ltr"><<a

                moz-do-not-send="true" href="mailto:qcolombet@apple.com"

                target="_blank">qcolombet@apple.com</a>></span>

            wrote:<br>

            <blockquote class="gmail_quote" style="margin:0 0 0

              .8ex;border-left:1px #ccc solid;padding-left:1ex">- Do we

              want to extend that to fatal error as well?<br>

              That would be a nice homogenization of the framework

              (replace (some of) the calls to report_fatal_error).<br>

            </blockquote>

            <div><br>

            </div>

            <div>This should definitely be used for things like "ran out

              of registers for inline asm".  That should only fail the

              current function codegen for something like MCJIT, and not

              exit the process.</div>

          </div>

        </div>

      </div>

    </blockquote>

    I strongly support Reid's stated objective of replacing fatal events

    with clean error exits where possible.  <br>

    <br>

    Philip<br>

  </body>

</html>