public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gcc-patches:master commit in: 14.0.0/gentoo/
Date: Wed,  7 Feb 2024 19:01:43 +0000 (UTC)	[thread overview]
Message-ID: <1707332496.31395f8bba7e15cd156c631946646f7c7799540d.sam@gentoo> (raw)

commit:     31395f8bba7e15cd156c631946646f7c7799540d
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Feb  7 19:01:36 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Feb  7 19:01:36 2024 +0000
URL:        https://gitweb.gentoo.org/proj/gcc-patches.git/commit/?id=31395f8b

14.0.0: drop upstream 76_all_PR113731-vect-crash.patch

Signed-off-by: Sam James <sam <AT> gentoo.org>

 14.0.0/gentoo/76_all_PR113731-vect-crash.patch | 13 -------------
 1 file changed, 13 deletions(-)

diff --git a/14.0.0/gentoo/76_all_PR113731-vect-crash.patch b/14.0.0/gentoo/76_all_PR113731-vect-crash.patch
deleted file mode 100644
index 671f11f..0000000
--- a/14.0.0/gentoo/76_all_PR113731-vect-crash.patch
+++ /dev/null
@@ -1,13 +0,0 @@
-https://gcc.gnu.org/PR113731
---- a/gcc/tree-vect-loop.cc
-+++ b/gcc/tree-vect-loop.cc
-@@ -11801,7 +11801,8 @@ move_early_exit_stmts (loop_vec_info loop_vinfo)
- 
-       gimple_stmt_iterator stmt_gsi = gsi_for_stmt (stmt);
-       gsi_move_before (&stmt_gsi, &dest_gsi);
--      gsi_prev (&dest_gsi);
-+      if (!gsi_end_p (dest_gsi))
-+       gsi_prev (&dest_gsi);
-     }
- 
-   /* Update all the stmts with their new reaching VUSES.  */


             reply	other threads:[~2024-02-07 19:01 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 19:01 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-07 23:25 [gentoo-commits] proj/gcc-patches:master commit in: 14.0.0/gentoo/ Sam James
2024-03-11 12:43 Sam James
2024-03-07 20:41 Sam James
2024-03-07 20:14 Sam James
2024-03-06 17:47 Sam James
2024-03-03 22:58 Sam James
2024-02-19  0:02 Sam James
2024-02-13 11:17 Sam James
2024-02-13 11:17 Sam James
2024-02-12  7:03 Sam James
2024-02-08 11:02 Sam James
2024-02-08 11:02 Sam James
2024-02-05  0:01 Sam James
2024-02-03  7:52 Sam James
2024-02-03  0:09 Sam James
2024-01-30 15:16 Sam James
2024-01-30 15:16 Sam James
2024-01-28 23:02 Sam James
2024-01-24 13:53 Sam James
2024-01-19  7:45 Sam James
2024-01-17  1:06 Sam James
2024-01-10 12:08 Sam James
2024-01-08  8:10 Sam James
2023-12-31 23:11 Sam James
2023-12-26 18:51 Sam James
2023-12-25 17:18 Sam James
2023-12-25 17:04 Sam James
2023-12-18  0:00 Sam James
2023-12-14 21:23 Sam James
2023-12-10 22:42 Sam James
2023-12-07 18:40 Sam James
2023-12-06 10:52 Sam James
2023-11-20  8:15 Sam James
2023-11-19 11:05 Sam James
2023-11-19 11:04 Sam James
2023-11-14  7:11 Sam James
2023-11-05 22:40 Sam James
2023-10-31 19:56 Sam James
2023-10-27 23:43 Sam James
2023-10-22 23:00 Sam James
2023-10-21 17:42 Sam James
2023-10-16 12:41 Sam James
2023-10-02 13:23 Sam James
2023-06-18 23:02 Sam James
2023-06-15 23:06 Sam James
2023-04-23 23:03 Sam James

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=1707332496.31395f8bba7e15cd156c631946646f7c7799540d.sam@gentoo \
    --to=sam@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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