[Bug other/55376] [asan] libsanitizer/README.gcc must contain the exact steps to do code changes and to port code from upstream

2012-11-20 Thread manu at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55376 Manuel López-Ibáñez manu at gcc dot gnu.org changed: What|Removed |Added CC||manu at gcc

[Bug other/55376] [asan] libsanitizer/README.gcc must contain the exact steps to do code changes and to port code from upstream

2012-11-20 Thread konstantin.s.serebryany at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55376 --- Comment #8 from Konstantin Serebryany konstantin.s.serebryany at gmail dot com 2012-11-21 04:23:21 UTC --- Why do you want to bother with a ChangeLog? I don't. I would prefer to simply mention the upstream revision to which was the

[Bug other/55376] [asan] libsanitizer/README.gcc must contain the exact steps to do code changes and to port code from upstream

2012-11-19 Thread ebotcazou at gcc dot gnu.org
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

[Bug other/55376] [asan] libsanitizer/README.gcc must contain the exact steps to do code changes and to port code from upstream

2012-11-19 Thread konstantin.s.serebryany at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55376 --- Comment #5 from Konstantin Serebryany konstantin.s.serebryany at gmail dot com 2012-11-20 05:40:34 UTC --- Merging in both directions is possible, but painful, so I'd prefer to limit it. How about this phrasing? === All changes

[Bug other/55376] [asan] libsanitizer/README.gcc must contain the exact steps to do code changes and to port code from upstream

2012-11-19 Thread ebotcazou at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55376 --- Comment #6 from Eric Botcazou ebotcazou at gcc dot gnu.org 2012-11-20 07:23:26 UTC --- === All changes in this directory should be pre-approved by one of the maintainers. Trivial and urgent fixes (portability, build fixes, etc)

[Bug other/55376] [asan] libsanitizer/README.gcc must contain the exact steps to do code changes and to port code from upstream

2012-11-18 Thread ebotcazou at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55376 Eric Botcazou ebotcazou at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW

[Bug other/55376] [asan] libsanitizer/README.gcc must contain the exact steps to do code changes and to port code from upstream

2012-11-18 Thread konstantin.s.serebryany at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55376 --- Comment #3 from Konstantin Serebryany konstantin.s.serebryany at gmail dot com 2012-11-18 18:47:19 UTC --- Are all upstream changes considered reviewed and automatically approved for gcc repo? all upstream changes are pre- or

[Bug other/55376] [asan] libsanitizer/README.gcc must contain the exact steps to do code changes and to port code from upstream

2012-11-17 Thread xinliangli at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55376 davidxl xinliangli at gmail dot com changed: What|Removed |Added CC||xinliangli