(In reply to Mike Hommey [:glandium] (high latency) from comment #24) > That specific comment explicitly says current GCC doesn't implement it. Are > we going to require clang only now?
Well GCC just fixed it in fairness: https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=279069 I think they would've fixed it much earlier if we would've found this on automation rather than after busting builds shipped by distros to a bunch of users... :) I think supporting clang-only would be sad, IMHO. I use gcc builds from time to time for debugging, as they have better debug info. (In reply to Nathan Froyd [:froydnj] from comment #23) > I'll just note that as somebody who has had multiple patches backed out > because of jobs that *only* run on central and those jobs aren't selectable > by default by `mach try fuzzy` (or non-obviously selectable), I'd really not > like to see us add more of "only run on m-c" jobs. To be clear, I'd be more than happy with them running in all pushes :) But if the automation cost is a concern, Tier2 + central-only shouldn't get anyone backed out, and should be cheaper, if I understand our backout policy correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850529 Title: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1850529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
