public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/55376] [asan] libsanitizer/README.gcc must contain the exact steps to do code changes and to port code from upstream Date: Mon, 19 Nov 2012 22:58:00 -0000 [thread overview] Message-ID: <bug-55376-4-mqmABK0uJo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55376-4@http.gcc.gnu.org/bugzilla/> 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.
next prev parent reply other threads:[~2012-11-19 22:58 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-18 4:07 [Bug other/55376] New: " konstantin.s.serebryany at gmail dot com 2012-11-18 5:18 ` [Bug other/55376] " xinliangli at gmail dot com 2012-11-18 9:30 ` ebotcazou at gcc dot gnu.org 2012-11-18 18:47 ` konstantin.s.serebryany at gmail dot com 2012-11-19 22:58 ` ebotcazou at gcc dot gnu.org [this message] 2012-11-20 5:41 ` konstantin.s.serebryany at gmail dot com 2012-11-20 7:23 ` ebotcazou at gcc dot gnu.org 2012-11-20 10:17 ` manu at gcc dot gnu.org 2012-11-21 4:24 ` konstantin.s.serebryany at gmail dot com 2012-11-23 10:57 ` [Bug sanitizer/55376] " konstantin.s.serebryany at gmail dot com 2012-11-23 12:45 ` konstantin.s.serebryany at gmail dot com 2012-11-23 12:57 ` konstantin.s.serebryany at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-55376-4-mqmABK0uJo@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).