On 03/03/2016 09:59 AM, Gregory Szorc wrote:
On Thu, Mar 3, 2016 at 8:09 AM, Erik Rose <e...@mozilla.com> wrote:
An additional bonus is that our ability to build with clang would break
less often. That's been the cause of more than a few scuttled DXR indexing
jobs.
We can and should have both Clang and GCC builds running in automation,
even if one of them is tier 2. We kinda/sorta have this with ASAN builds,
which are Clang. We don't necessary need tests to run - just a smoke test
of the build.
And we have this with rooting hazard analysis builds, which are GCC.
This thread terrifies me somewhat, because it makes me think that either
I will be the last user of GCC at some point and so will need to deal
with all of the GCC-only breakage, or I'll have to port the hazard
analysis over to clang. Neither of those sounds like a lot of fun. But
I'll deal with it one way or the other when I need to.
(The hazard analysis is implemented as a GCC plugin that first converts
GCC's internal control flow graph output into a much-simplified graph,
then the analysis crawls over that graph. The second part should be
mostly reusable, but the first part has lots of weird knowledge built
into it about different forms and special cases.)
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
