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.2.1-6
Date: Mon, 29 Jun 2026 12:30:44 GMT	[thread overview]
Message-ID: <178273624442.1.15098544476013894499.rpms-gcc-02c34dfa3627@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/gcc
Branch : rhel-f41-base
Commit : 02c34dfa3627ef05d676d30e152a66e77b58529b
Author : Jakub Jelinek <jakub@redhat.com>
Date   : 2024-11-04T16:02:03+01:00
Stats  : +12/-4 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/gcc/c/02c34dfa3627ef05d676d30e152a66e77b58529b?branch=rhel-f41-base

Log:
14.2.1-6

---
diff --git a/.gitignore b/.gitignore
index 457da17..a0bbeb8 100644
--- a/.gitignore
+++ b/.gitignore
@@ -26,3 +26,4 @@
 /gcc-14.2.1-20240905.tar.xz
 /gcc-14.2.1-20240912.tar.xz
 /gcc-14.2.1-20241025.tar.xz
+/gcc-14.2.1-20241104.tar.xz

diff --git a/gcc.spec b/gcc.spec
index 6b499c8..e74627b 100644
--- a/gcc.spec
+++ b/gcc.spec
@@ -1,10 +1,10 @@
-%global DATE 20241025
-%global gitrev 3f6cf880bdadb4404d5540bad605ceec58261359
+%global DATE 20241104
+%global gitrev b84ce6a258e01f6559a1855b5f1d1ba4e69a927b
 %global gcc_version 14.2.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 5
+%global gcc_release 6
 %global nvptx_tools_gitrev 87ce9dc5999e5fca2e1d3478a30888d9864c9804
 %global newlib_cygwin_gitrev d45261f62a15f8abd94a1031020b9a9f455e4eed
 %global _unpackaged_files_terminate_build 0
@@ -3620,6 +3620,13 @@ end
 %endif
 
 %changelog
+* Mon Nov  4 2024 Jakub Jelinek <jakub@redhat.com> 14.2.1-6
+- update from releases/gcc-14 branch
+  - PRs fortran/79685, jit/117275, libstdc++/117321, libstdc++/117406,
+	middle-end/117354, rtl-optimization/116783, rtl-optimization/117327,
+	target/116415, target/117296, target/117318, tree-optimization/107467,
+	tree-optimization/117287
+
 * Fri Oct 25 2024 Jakub Jelinek <jakub@redhat.com> 14.2.1-5
 - update from releases/gcc-14 branch
   - PRs ada/114593, ada/114636, ada/114640, ada/115535, ada/116190,

diff --git a/sources b/sources
index 27042d2..df7802d 100644
--- a/sources
+++ b/sources
@@ -1,4 +1,4 @@
-SHA512 (gcc-14.2.1-20241025.tar.xz) = 1729619d7c0ebdb6801f692f213ccdd2f393d28d2c2acc3cedc897992c0996d45d760e9f4bd4d6f3ef16c7343a1e24c21c45989fa6c08ba1556fa8c9a5662d5f
+SHA512 (gcc-14.2.1-20241104.tar.xz) = 4a453e1b7e2712fd2a12d28cf2aaf8e76c789f7e747218cdf867eaca84e381305bf119c7db873c5c3f0981657dbefcded77ad74a0960034b95232d906e4b02d0
 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=178273624442.1.15098544476013894499.rpms-gcc-02c34dfa3627@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