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

unknown user pushed a change to branch hjl/interrupt/stage1 in repository gcc.

discards 75b031c Implement x86 interrupt attribute discards eb942fb Update TARGET_FUNCTION_INCOMING_ARG documentation adds fcc8620 Revert "Improve verification of loop->latch in verify_loop_st [...] new d9d5067 Update TARGET_FUNCTION_INCOMING_ARG documentation new de6940a Implement x86 interrupt attribute

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 (75b031c) \ N -- N -- N refs/heads/hjl/interrupt/stage1 (de6940a)

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 2 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/ChangeLog | 11 +++++++++ gcc/cfgloop.c | 70 +++++++++++++++++----------------------------------------- gcc/cfgloop.h | 1 - gcc/function.c | 2 +- gcc/omp-low.c | 1 - 5 files changed, 32 insertions(+), 53 deletions(-)