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 cc02d7d gcc.target/i386/pieces-memset-1.c discards 7b2426f Properly align stack in gcc.target/i386/cleanup-[12].c discards f5cdc40 Update i386 piecewise move and store discards 2982ccf Remove MAX_BITSIZE_MODE_ANY_INT discards 74181d3 Add TARGET_GEN_MEMSET_VALUE discards 4d90a18 Update alignment_for_piecewise_move discards d46b16e Extend STV pass to 64-bit mode new f59b80a Extend STV pass to 64-bit mode new 7111e85 Update alignment_for_piecewise_move new 8bb26c6 Add TARGET_GEN_MEMSET_VALUE new 61c380f Remove MAX_BITSIZE_MODE_ANY_INT new 4f07b58 Update i386 piecewise move and store new 0fa724b Properly align stack in gcc.target/i386/cleanup-[12].c new 4acf3cc 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 (cc02d7d) \ N -- N -- N refs/heads/hjl/pieces/master (4acf3cc)
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/testsuite/gcc.target/i386/pr55247-2.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)