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 150da50 Update i386 piecewise move and store discards 1ae2d5d Remove MAX_BITSIZE_MODE_ANY_INT discards 28da365 Add TARGET_GEN_MEMSET_VALUE discards 7b0daab Update alignment_for_piecewise_move discards c9b0a3a Extend STV pass to 64-bit mode discards 4999401 Allow all 1s of integer as standard SSE constants adds 6f9d277 Daily bump. adds 5a8ec50 Allow all 1s of integer as standard SSE constants adds 47feda3 Extend STV pass to 64-bit mode new 4c1b32a Update alignment_for_piecewise_move new abba6ff Add TARGET_GEN_MEMSET_VALUE new 98224a4 Remove MAX_BITSIZE_MODE_ANY_INT new ee55bec 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 (150da50) \ N -- N -- N refs/heads/hjl/pieces/master (ee55bec)
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 4 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/DATESTAMP | 2 +- gcc/config/i386/i386.c | 5 ++++- 2 files changed, 5 insertions(+), 2 deletions(-)