This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch hjl/indirect/gcc-7-branch/master in repository gcc.
discards 13dce7cceef x86: Disallow -mindirect-branch=/-mfunction-return= with -m [...] discards 5e977dfedb9 x86: Add 'V' register operand modifier discards 139dd2c61a1 x86: Add -mindirect-branch-register discards dfa5f37da1f x86: Add -mfunction-return= discards 09f7c546376 x86: Add -mindirect-branch= new c1f10551514 x86: Add -mindirect-branch= new aa26b6fbdf8 x86: Add -mfunction-return= new 95ec88783e8 x86: Add -mindirect-branch-register new 3b73022d2a2 x86: Add 'V' register operand modifier new a3144b575e1 x86: Disallow -mindirect-branch=/-mfunction-return= with -m [...]
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:
* -- * -- B -- O -- O -- O (13dce7cceef) \ N -- N -- N refs/heads/hjl/indirect/gcc-7-branch/master (a3144b575e1)
You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.
Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.
The 5 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.
Summary of changes: