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: 14.3.1-2
Date: Mon, 29 Jun 2026 12:30:48 GMT	[thread overview]
Message-ID: <178273624812.1.4562602495266159009.rpms-gcc-1afae6de5343@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/gcc
Branch : rhel-f41-base
Commit : 1afae6de5343fe1efa6c3885a9b69de1dcf79375
Author : Jakub Jelinek <jakub@redhat.com>
Date   : 2025-06-17T08:52:43+02:00
Stats  : +13/-4 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/gcc/c/1afae6de5343fe1efa6c3885a9b69de1dcf79375?branch=rhel-f41-base

Log:
14.3.1-2

---
diff --git a/.gitignore b/.gitignore
index 577035f..6cb3493 100644
--- a/.gitignore
+++ b/.gitignore
@@ -30,3 +30,4 @@
 /gcc-14.2.1-20250110.tar.xz
 /gcc-14.2.1-20250210.tar.xz
 /gcc-14.3.1-20250523.tar.xz
+/gcc-14.3.1-20250617.tar.xz

diff --git a/gcc.spec b/gcc.spec
index 826b804..fa6570c 100644
--- a/gcc.spec
+++ b/gcc.spec
@@ -1,10 +1,10 @@
-%global DATE 20250523
-%global gitrev 078cfa03d84e31681f7115a2437e83ea9a7bf382
+%global DATE 20250617
+%global gitrev 74a421064f3d0de5d604bc051d9c21c1b9763064
 %global gcc_version 14.3.1
 %global gcc_major 14
 # 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 1
+%global gcc_release 2
 %global nvptx_tools_gitrev 87ce9dc5999e5fca2e1d3478a30888d9864c9804
 %global newlib_cygwin_gitrev d45261f62a15f8abd94a1031020b9a9f455e4eed
 %global _unpackaged_files_terminate_build 0
@@ -3620,6 +3620,14 @@ end
 %endif
 
 %changelog
+* Tue Jun 17 2025 Jakub Jelinek <jakub@redhat.com> 14.3.1-2
+- update from releases/gcc-14 branch
+  - PRs c++/120123, c++/120161, fortran/85750, fortran/98454, libstdc++/99832,
+	libstdc++/120548, middle-end/117811, middle-end/118819,
+	middle-end/120547, rtl-optimization/117239, target/86772,
+	target/119834, target/120441, target/120480, testsuite/52641,
+	tree-optimization/117358, tree-optimization/120638
+
 * Fri May 23 2025 Jakub Jelinek <jakub@redhat.com> 14.3.1-1
 - update from releases/gcc-14 branch
   - GCC 14.3 release

diff --git a/sources b/sources
index a127d1b..edadb95 100644
--- a/sources
+++ b/sources
@@ -1,4 +1,4 @@
-SHA512 (gcc-14.3.1-20250523.tar.xz) = 6f6cd40893a5ce7de9ef74da63b50e60ebe6ec1a9a847b3ea37cc2cec2177d292a9c1963f78aa223f8a25a4ebefc2ef81ea940521fea16375d6512edda8aaa30
+SHA512 (gcc-14.3.1-20250617.tar.xz) = 5b5f35f56e6e3ddcb94a72756af316b6520bd4c3d740553c88f99d91101bd99a6e4d50b7cd677159327b08bc91903939e97f1004f2dfaabd2085501e63dc061e
 SHA512 (isl-0.24.tar.bz2) = aab3bddbda96b801d0f56d2869f943157aad52a6f6e6a61745edd740234c635c38231af20bc3f1a08d416a5e973a90e18249078ed8e4ae2f1d5de57658738e95
 SHA512 (newlib-cygwin-d45261f62a15f8abd94a1031020b9a9f455e4eed.tar.xz) = 31bfc19429797236e268e22b752c5abeabb9c0f39b1058634af8dab329b4f028fc72a35888193c9575f6cee5cf2c069669d79fcb4d4e3a4318f57413452f707d
 SHA512 (nvptx-tools-87ce9dc5999e5fca2e1d3478a30888d9864c9804.tar.xz) = 941e763af8601b89f0e4ec48a2d68ae0a8e70ee1e6ba6859394b021ad7bd7d143cc529f3c35c08d7f84e5554980ddcc97cf05b6c4755c2bc36c91161b79e8cea

                 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=178273624812.1.4562602495266159009.rpms-gcc-1afae6de5343@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