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

unknown user pushed a change to branch hjl/pieces/master in repository gcc.

discards 22601be gcc.target/i386/pieces-memset-1.c discards 503f590 Properly align stack in gcc.target/i386/cleanup-[12].c discards cb667e1 Update i386 piecewise move and store discards d630944 Remove MAX_BITSIZE_MODE_ANY_INT discards ea6cb3c Add TARGET_GEN_MEMSET_VALUE discards 1279691 Update alignment_for_piecewise_move discards daa064a Extend STV pass to 64-bit mode new fc21f17 Extend STV pass to 64-bit mode new e248a4f Update alignment_for_piecewise_move new dd2b3a2 Add TARGET_GEN_MEMSET_VALUE new 07ecda8 Remove MAX_BITSIZE_MODE_ANY_INT new d1808ea Update i386 piecewise move and store new 7723b79 Properly align stack in gcc.target/i386/cleanup-[12].c new e0c91f9 gcc.target/i386/pieces-memset-1.c

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 (22601be) \ N -- N -- N refs/heads/hjl/pieces/master (e0c91f9)

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 7 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/config/i386/i386.c | 3 +++ 1 file changed, 3 insertions(+)