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] (10 commits) Add new test-case. Date: Mon, 8 Nov 2021 15:36:18 +0000 (GMT) [thread overview] Message-ID: <20211108153618.C45153858003@sourceware.org> (raw) The branch 'marxin/heads/loop-unswitching-switch-v5' was updated to point to: e90e6fe2afc... Add new test-case. It previously pointed to: 5506d47cd1b... Restore old code that can handle floating point types. Diff: !!! WARNING: THE FOLLOWING COMMITS ARE NO LONGER ACCESSIBLE (LOST): ------------------------------------------------------------------- 5506d47... Restore old code that can handle floating point types. 5694683... Revert "Use global ranger." 5df2804... Use global ranger. 0534ab9... Simplify usage of rangers. 0e261eb... Loop unswitching: support gswitch statements. Summary of changes (added commits): ----------------------------------- 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. d626fe7... Fix spurious valgrind errors in irred loop verification (*) 1854694... path solver: Avoid recalculating ranges already in the cach (*) a354b42... rs6000: Miscellaneous uses of rs6000_builtins_decl_x (*) 71cf7c0... rs6000: Update rs6000_builtin_decl (*) (*) 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-08 15:36 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=20211108153618.C45153858003@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: linkBe 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).