http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55376
--- Comment #4 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-11-19 22:58:17 UTC --- > I've got your point, but please understand mine: if the trees go too much out > of sync we (the asan team) will lose control over one of the copies (gcc). > It will mean that some one else (not us) will have to work on asan in gcc. > Maybe that's not bad, but I don't want it. You're the maintainers, so you can merge in both directions. > As I understood from previous e-mails, there are libraries with similar > problems in the gcc tree. What are the solutions there? libffi is merged in both directions but is not very active. For the Go compiler, Ian first applies the patches upstream and then merges in the GCC tree. > It's great that such regressions is acceptable, but if there is an > infrastructure that allows us to know about possible regressions before the > commit (aka try bots), I'd like to know. No, there is no automated command&control tool for the all the platforms, you'll have to deal with humans for most of them.
