Started 8 mo 16 days ago
Took 1 hr 20 min on green-dragon-17

Success Build rL:372346 - C:372334 - #679 (Sep 19, 2019 11:41:13 AM)

  • : 372346
  • : 372334
  • : 372312
  • : 364589
  • : 372342
  • : 372242
  • : 372317
  1. [Analysis] Allow -scalar-evolution-max-iterations more than once

    At present, `-scalar-evolution-max-iterations` is a `cl::Optional`
    option, which means it demands to be passed exactly zero or one times.
    Our build system makes it pretty tricky to guarantee this. We often
    accidentally pass the flag more than once (but always with the same
    value) which results in an error, after which compilation fails:

    clang (LLVM option parsing): for the -scalar-evolution-max-iterations option: may only occur zero or one times!

    It seems reasonable to allow -scalar-evolution-max-iterations to be
    passed more than once. Quoting the [[ | documentation ]]:

    > The cl::ZeroOrMore modifier ... indicates that your program will allow the option to be specified zero or more times.
    > ...
    > If an option is specified multiple times for an option of the cl::opt class, only the last value will be retained.

    Original patch by: Enrico Bern Hardy Tanuwidjaja <>

    Differential Revision: (detail/ViewSVN)
    by smeenai
  2. [NFC][PowerPC] Fast-isel VSX support test

    We have fixed most of the VSX limitation in Fast-isel,
    so we can remove the -mattr=-vsx for most testcases now. (detail/ViewSVN)
    by jsji

Started by an SCM change

This run spent:

  • 19 min waiting;
  • 1 hr 20 min build duration;
  • 1 hr 39 min total from scheduled to completion.
LLVM/Clang Warnings: 1 warning.
    Test Result (no failures)