http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55376
Bug #: 55376
Summary: [asan] libsanitizer/README.gcc must contain the exact
steps to do code changes and to port code from
upstream
Classification: Unclassified
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: konstantin.s.serebry...@gmail.com
CC: dseke...@redhat.com, dvyu...@google.com,
ja...@redhat.com, w...@gcc.gnu.org
We need to document the libsanitizer update process in libsanitizer/README.gcc
Few things to cover:
- The changes need to be approved by one of the maintainers (or is it obvious)?
- Except for *really* trivial changes all patches should go through the
upstream tree first.
- When updating from upstream, the comment header should be tampered with (oh,
my)
- Ideally, we need to have a fully automated script to grab the upstream
changes (including new/deleted/moved files, etc). Suggestions here?
- What is the testing procedure when updating from upstream? (e.g. how do we
avoid regressions on the platforms to which the maintainers have no access?)
