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: 12.0.0-0.5.1
Date: Mon, 29 Jun 2026 12:29:34 GMT	[thread overview]
Message-ID: <178273617446.1.16364773997786268176.rpms-gcc-dca274fd43c5@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/gcc
Branch : rhel-f41-base
Commit : dca274fd43c5b243531f8cd5b480f7ddeee773d6
Author : Jakub Jelinek <jakub@redhat.com>
Date   : 2022-01-15T00:19:21+01:00
Stats  : +7/-1 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/gcc/c/dca274fd43c5b243531f8cd5b480f7ddeee773d6?branch=rhel-f41-base

Log:
12.0.0-0.5.1

---
diff --git a/gcc.spec b/gcc.spec
index b08c733..598eb4d 100644
--- a/gcc.spec
+++ b/gcc.spec
@@ -119,7 +119,7 @@
 Summary: Various compilers (C, C++, Objective-C, ...)
 Name: gcc
 Version: %{gcc_version}
-Release: %{gcc_release}.5%{?dist}
+Release: %{gcc_release}.5.1%{?dist}
 # libgcc, libgfortran, libgomp, libstdc++ and crtstuff have
 # GCC Runtime Exception.
 License: GPLv3+ and GPLv3+ with exceptions and GPLv2+ with exceptions and LGPLv2+ and BSD
@@ -993,6 +993,9 @@ CONFIGURE_OPTS="\
 %ifarch sparc sparcv9 sparc64 ppc ppc64 ppc64le ppc64p7 s390 s390x alpha
 	--with-long-double-128 \
 %endif
+%ifarch ppc64le
+	--with-long-double-format=ieee \
+%endif
 %ifarch sparc
 	--disable-linux-futex \
 %endif
@@ -3146,6 +3149,9 @@ end
 %endif
 
 %changelog
+* Sat Jan 15 2022 Jakub Jelinek <jakub@redhat.com> 12.0.0-0.5.1
+- default to -mabi=ieeelongdouble on ppc64le
+
 * Sat Jan 15 2022 Jakub Jelinek <jakub@redhat.com> 12.0.0-0.5
 - update from trunk
   - PRs ada/104027, analyzer/104029, c++/70417, c++/103705, c++/103991,

                 reply	other threads:[~2026-06-29 12:29 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=178273617446.1.16364773997786268176.rpms-gcc-dca274fd43c5@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