This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch jason/concepts-rewrite in repository gcc.
discards 0d0b028 tsubst_args discards d184b43 no-workaround discards e2aa7df equal_check_constr discards 9c35915 * search.c (accessible_p): Don't shortcut when evaluating co [...] discards d20dfff overloaded_operator_p new ecf81ba uses_outer-assoc new 6a0b31e overloaded_operator_p new 0c62078 * search.c (accessible_p): Don't shortcut when evaluating co [...] new 2aa2c7d equal_check_constr new d0fd509 no-workaround new 34748b7 tsubst_args new 38f39fe constraint_memo new 9ca3f11 remove-assumptions new 837f716 static new db575ea arg-select new c536c71 expr
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 (0d0b028) \ N -- N -- N refs/heads/jason/concepts-rewrite (c536c71)
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 11 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: gcc/cp/constraint.cc | 87 ++++++++++++++++++++++++++++++---------------------- gcc/cp/cp-tree.h | 16 ---------- gcc/cp/pt.c | 28 ++++++----------- gcc/cp/ptree.c | 1 - 4 files changed, 60 insertions(+), 72 deletions(-)