Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-1210

Print nicer FATAL message when required CPU flags are not present

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: Public beta
    • Fix Version/s: 0.6.0
    • Component/s: util
    • Labels:
      None

      Description

      Currently if a user tries to run Kudu on a machine that doesn't have SSSE3 or SSE4.2, they get a SIGILL when we try to run a instruction from those instruction sets. Instead, we should check for those flags at startup and FATAL with a nice message.

      If this turns out to limit adoption, we can put in some effort to cordon off the SSE-enabled parts of the code and provide non-SSE alternatives.

        Attachments

          Activity

            People

            • Assignee:
              tlipcon Todd Lipcon
              Reporter:
              tlipcon Todd Lipcon
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: