public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/gcc] rhel-f41-base: 13.1.1-3
Date: Mon, 29 Jun 2026 12:30:15 GMT	[thread overview]
Message-ID: <178273621543.1.1555529182303287143.rpms-gcc-8f1aceb90bee@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/gcc
Branch : rhel-f41-base
Commit : 8f1aceb90beea8c643f2debf68f3bcbe00bc8348
Author : Jakub Jelinek <jakub@redhat.com>
Date   : 2023-05-19T11:26:04+02:00
Stats  : +12/-4 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/gcc/c/8f1aceb90beea8c643f2debf68f3bcbe00bc8348?branch=rhel-f41-base

Log:
13.1.1-3

---
diff --git a/.gitignore b/.gitignore
index a274f6a..ad9cdaa 100644
--- a/.gitignore
+++ b/.gitignore
@@ -105,3 +105,4 @@
 /gcc-13.0.1-20230421.tar.xz
 /gcc-13.1.1-20230426.tar.xz
 /gcc-13.1.1-20230511.tar.xz
+/gcc-13.1.1-20230519.tar.xz

diff --git a/gcc.spec b/gcc.spec
index 37709e6..5dedde9 100644
--- a/gcc.spec
+++ b/gcc.spec
@@ -1,10 +1,10 @@
-%global DATE 20230511
-%global gitrev 55ca611b161ce96d568ea82ff0e6ea395dc76957
+%global DATE 20230519
+%global gitrev 75b6adf0fdb4d09b64cddfdce59a030f69071fc5
 %global gcc_version 13.1.1
 %global gcc_major 13
 # Note, gcc_release must be integer, if you want to add suffixes to
 # %%{release}, append them after %%{gcc_release} on Release: line.
-%global gcc_release 2
+%global gcc_release 3
 %global nvptx_tools_gitrev 93e00909ceb9cbbc104f0fcba56c0361ffb3ca4b
 %global newlib_cygwin_gitrev 9e09d6ed83cce4777a5950412647ccc603040409
 %global _unpackaged_files_terminate_build 0
@@ -3459,6 +3459,13 @@ end
 %endif
 
 %changelog
+* Fri May 19 2023 Jakub Jelinek <jakub@redhat.com> 13.1.1-3
+- update from releases/gcc-13 branch
+  - PRs c++/80488, c++/83258, c++/97700, c++/103807, c++/109651, c++/109745,
+	c++/109761, c++/109774, c++/109868, c++/109884, fortran/109641,
+	fortran/109846, libstdc++/109816, libstdc++/109883, target/104338,
+	target/109697
+
 * Thu May 11 2023 Jakub Jelinek <jakub@redhat.com> 13.1.1-2
 - update from releases/gcc-13 branch
   - PRs c++/91618, c++/96604, c++/109506, c++/109640, c++/109642, c++/109666,

diff --git a/sources b/sources
index 7a82c78..92b1935 100644
--- a/sources
+++ b/sources
@@ -1,4 +1,4 @@
-SHA512 (gcc-13.1.1-20230511.tar.xz) = 0ba5b1db652992b1abd356ac36a48c9db4ecd01c751ae3488dd8680199e678845d59bfb4b8d747b91bca258ea8d5a2c274f3bbb2039dd4de2f65942dd902a616
+SHA512 (gcc-13.1.1-20230519.tar.xz) = 7969a54b13b9852790728ddb460297a899413fbfdf872f0ca06b4a1600cf6cafb532be6ec176f51abcde1f3cf0d87f8ac948e241ff20f152443c9c8d3eaf8455
 SHA512 (isl-0.24.tar.bz2) = aab3bddbda96b801d0f56d2869f943157aad52a6f6e6a61745edd740234c635c38231af20bc3f1a08d416a5e973a90e18249078ed8e4ae2f1d5de57658738e95
 SHA512 (newlib-cygwin-9e09d6ed83cce4777a5950412647ccc603040409.tar.xz) = bef3fa04f7b1a915fc1356ebed114698b5cc835e9fa04b0becff05a9efc76c59fb376482990873d222d7acdcfee3c4f30f5a4cb7f3be1f291f1fa5f1c7a9d983
 SHA512 (nvptx-tools-93e00909ceb9cbbc104f0fcba56c0361ffb3ca4b.tar.xz) = c719fad8689b2b6f3c888d0308604ddef884037d71ec3e755c68052d30075a181c29358fda516833ace437921b17602b147be7886317be94ec9736faa8cb52be

                 reply	other threads:[~2026-06-29 12:30 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=178273621543.1.1555529182303287143.rpms-gcc-8f1aceb90bee@fedoraproject.org \
    --to=jakub@redhat.com \
    --cc=git-commits@fedoraproject.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