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 97d2abf Remove ix86_duplicated_const_wide_int discards 771d097 Handle push and all ones for OImode and XImode discards 5b054ba Update i386 piece move/store discards f8f5946 Remove MAX_BITSIZE_MODE_ANY_INT new 8fbb5d8 Update alignment_for_piecewise_move new 8ffeb22 Add TARGET_GEN_MEMSET_VALUE new 59b94fc Allow all 1s of integer as standard SSE constants new eb569c06 Remove MAX_BITSIZE_MODE_ANY_INT new da5c585 Update i386 piecewise move and store

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 (97d2abf) \ N -- N -- N refs/heads/hjl/pieces/master (da5c585)

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/config/i386/i386.c | 41 ++++++++++++++++++++--------------------- gcc/config/i386/i386.md | 4 ++-- gcc/targhooks.h | 20 -------------------- 3 files changed, 22 insertions(+), 43 deletions(-)