This is an automated email from the git hooks/post-receive script.

unknown user pushed a change to branch aoliva/testme in repository gcc.

discards 4dbc22222ae [IEPM] Introduce debug hook for inline entry point markers discards f41cdce6289 [SFN] Introduce -gstatement-frontiers option, enable debug markers discards dd81e9738d3 [SFN] introduce statement frontier notes, still disabled discards ebb989f937b [SFN] stabilize find_bb_boundaries discards 7de4828cf24 [SFN] not-quite-boilerplate changes in preparation to intro [...] new 72cd131af37 [SFN] not-quite-boilerplate changes in preparation to intro [...] new 2e1fcd438f0 [SFN] stabilize find_bb_boundaries new 7a1ed3c180b [SFN] introduce statement frontier notes, still disabled new 47966987de8 [SFN] Introduce -gstatement-frontiers option, enable debug markers new 8a8ab0e880b [IEPM] Introduce debug hook for inline entry point markers

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 (4dbc22222ae) \ N -- N -- N refs/heads/aoliva/testme (8a8ab0e880b)

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: gcc/gimple-loop-interchange.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)