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 7a78515 Check --with-arch=/--with-arch-32= for 32-bit x86 libitm library discards f6d9683 Check --with-arch=/--with-arch-32= for 32-bit x86 libgomp library discards 732f084 Check --with-arch=/--with-arch-32= for 32-bit x86 libatomic library new 4202c33 Don't build 32-bit libatomic with -march=i486 on x86-64 new 1c1d4fc Don't build 32-bit libgomp with -march=i486 on x86-64 new aafc496 Don't build 32-bit libitm with -march=i486 on x86-64
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 (7a78515) \ N -- N -- N refs/heads/hjl/pieces/master (aafc496)
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: libatomic/configure.tgt | 14 ++------------ libgomp/configure.tgt | 11 ++--------- libitm/configure.tgt | 12 ++---------- 3 files changed, 6 insertions(+), 31 deletions(-)