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

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

discards 02533ef Only allow aligned memory on SSE *mov<mode>_internal discards 36be0bb Remove ssememalign discards ae7dbff Remove ix86_legitimate_combined_insn discards 98fa87f Use vector_operand on SSE with 16b memory operand discards f497be1 Add vector_memory_operand and "Bm" constraint adds 359eb7f Daily bump. adds 57f928f * doc/invoke.texi (Warning Options): Document -Winvalid-memor [...] adds 813cfbb PR target/66655 * config/i386/cygming.h (MAKE_DECL_ONE_ONLY [...] new a4784cd Add vector_memory_operand and "Bm" constraint new 7207c4d Use vector_operand on SSE with 16b memory operand new 276d672 Remove ix86_legitimate_combined_insn new e2c9193 Remove ssememalign new c120975 Only allow aligned memory on SSE *mov<mode>_internal

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 (02533ef) \ N -- N -- N refs/heads/hjl/pr68991/master (c120975)

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/ChangeLog | 10 ++++++++++ gcc/DATESTAMP | 2 +- gcc/config/i386/constraints.md | 2 +- gcc/config/i386/cygming.h | 5 +++++ gcc/doc/invoke.texi | 22 +++++++++++++++++++++- 5 files changed, 38 insertions(+), 3 deletions(-)