This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch hjl/pr70155/bitwise in repository gcc.
discards e88a8ea check_non_convertible_reg_64 to void discards 16ff4c2 Fix Add zext to TI patterns for 64-bit STV discards f347429 Add zext to TI patterns for 64-bit STV discards 6d94f8b Change check_non_convertible_reg_64 to return bool discards dffc128 Add TI bitwise operations to 64-bit STV discards 791a6f9 Add <any_logic>ti3 new 6ab73f2 Add <any_logic>ti3 and <any_logic>v1ti3 patterns new a987e39 Add zext to TI patterns for 64-bit STV new e35caeb Add TI bitwise operations to 64-bit STV
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 (e88a8ea) \ N -- N -- N refs/heads/hjl/pr70155/bitwise (e35caeb)
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 3 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 | 222 +++++++++++++++++++++++++++---------------------- 1 file changed, 124 insertions(+), 98 deletions(-)