public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/marxin/heads/loop-unswitching-switch-v5] (13 commits) Loop unswitching: support gswitch statements.
Date: Tue,  9 Nov 2021 10:05:56 +0000 (GMT)	[thread overview]
Message-ID: <20211109100556.64C03385801D@sourceware.org> (raw)

The branch 'marxin/heads/loop-unswitching-switch-v5' was updated to point to:

 cf96b955f5a... Loop unswitching: support gswitch statements.

It previously pointed to:

 ab516cc5de2... Add missing update_stmt.

Diff:

!!! WARNING: THE FOLLOWING COMMITS ARE NO LONGER ACCESSIBLE (LOST):
-------------------------------------------------------------------

  ab516cc... Add missing update_stmt.
  a19c463... Add tree-dump times.
  e90e6fe... Add new test-case.
  31102db... Restore old code that can handle floating point types.
  7f763ce... Revert "Use global ranger."
  3a37d89... Use global ranger.
  40938b4... Simplify usage of rangers.
  5c6911e... Loop unswitching: support gswitch statements.


Summary of changes (added commits):
-----------------------------------

  cf96b95... Loop unswitching: support gswitch statements.
  5acf02c... Ranger - grow.
  69b6cce... Fix clang -Wcast-qual warning. (*)
  2abd924... Minor optimization of variable bit testing (*)
  1bd8983... Daily bump. (*)
  206c08c... rs6000: Add escape-newline support for builtins files (*)
  6c5fffd... Fix couple of issues in large PIC model on x86-64/VxWorks (*)
  d44d791... Remove workaround allowing interposition of nested function (*)
  0cd653b... Don't calculate new values when using the private context c (*)
  33a7a63... Improve handling of some builtins. (*)
  666d780... Move uncprop after modref (*)
  239d82d... ipa: Unshare expresseions before putting them into debug st (*)
  a7dce76... powerpc: Fix vsx_splat_v4si_di breakage on Power8. (*)

(*) This commit already exists in another branch.
    Because the reference `refs/users/marxin/heads/loop-unswitching-switch-v5' matches
    your hooks.email-new-commits-only configuration,
    no separate email is sent for this commit.


                 reply	other threads:[~2021-11-09 10:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211109100556.64C03385801D@sourceware.org \
    --to=marxin@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).