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: Clean up last change
Date: Mon, 29 Jun 2026 12:26:05 GMT	[thread overview]
Message-ID: <178273596532.1.15526906242053771014.rpms-gcc-39f49505ef60@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/gcc
Branch : rhel-f41-base
Commit : 39f49505ef603d3fd32e4341e3835f22f6114bf6
Author : Jakub Jelinek <jakub@redhat.com>
Date   : 2014-02-20T15:06:38+01:00
Stats  : +19/-17 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/gcc/c/39f49505ef603d3fd32e4341e3835f22f6114bf6?branch=rhel-f41-base

Log:
Clean up last change

---
diff --git a/gcc.spec b/gcc.spec
index 93dcc23..b66efcc 100644
--- a/gcc.spec
+++ b/gcc.spec
@@ -198,7 +198,7 @@ Patch13: gcc48-pr56564.patch
 Patch14: gcc48-pr56493.patch
 Patch15: gcc48-color-auto.patch
 Patch16: gcc48-pr28865.patch
-Patch17: gcc48-aarch64-define-TRY_EMPTY_VM_SPACE.patch
+Patch17: gcc48-pr60010.patch
 
 Patch1000: fastjar-0.97-segfault.patch
 Patch1001: fastjar-0.97-len1.patch
@@ -759,7 +759,7 @@ package or when debugging this package.
 %patch15 -p0 -b .color-auto~
 %endif
 %patch16 -p0 -b .pr28865~
-%patch17 -p1 -b .aarch64-pch~
+%patch17 -p0 -b .pr60010~
 
 %if 0%{?_enable_debug_packages}
 cat > split-debuginfo.sh <<\EOF
@@ -3028,7 +3028,7 @@ fi
 
 %changelog
 * Fri Jan 31 2014 Kyle McMartin <kyle@redhat.com> 4.8.2-14
-- aarch64: fix cc1plus segfault using pch (#1058991), PR pch/60010
+- fix pch on aarch64 (#1058991, PR pch/60010)
 
 * Tue Jan 21 2014 Jakub Jelinek <jakub@redhat.com> 4.8.2-13
 - when removing -Wall from CXXFLAGS, if -Werror=format-security

diff --git a/gcc48-aarch64-define-TRY_EMPTY_VM_SPACE.patch b/gcc48-aarch64-define-TRY_EMPTY_VM_SPACE.patch
deleted file mode 100644
index 4e54e05..0000000
--- a/gcc48-aarch64-define-TRY_EMPTY_VM_SPACE.patch
+++ /dev/null
@@ -1,14 +0,0 @@
-http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60010
-https://bugzilla.redhat.com/show_bug.cgi?id=1058991
-
---- a/gcc/config/host-linux.c
-+++ b/gcc/config/host-linux.c
-@@ -86,6 +86,8 @@
- # define TRY_EMPTY_VM_SPACE	0x60000000
- #elif defined(__mc68000__)
- # define TRY_EMPTY_VM_SPACE	0x40000000
-+#elif defined(__aarch64__)
-+# define TRY_EMPTY_VM_SPACE	0x1000000000
- #elif defined(__ARM_EABI__)
- # define TRY_EMPTY_VM_SPACE     0x60000000
- #elif defined(__mips__) && defined(__LP64__)

diff --git a/gcc48-pr60010.patch b/gcc48-pr60010.patch
new file mode 100644
index 0000000..0baa553
--- /dev/null
+++ b/gcc48-pr60010.patch
@@ -0,0 +1,16 @@
+2014-02-14  Kyle McMartin  <kyle@redhat.com>
+
+	PR pch/60010
+	* config/host-linux.c (TRY_EMPTY_VM_SPACE): Define for AArch64.
+
+--- gcc/config/host-linux.c	(revision 207784)
++++ gcc/config/host-linux.c	(revision 207785)
+@@ -86,6 +86,8 @@
+ # define TRY_EMPTY_VM_SPACE	0x60000000
+ #elif defined(__mc68000__)
+ # define TRY_EMPTY_VM_SPACE	0x40000000
++#elif defined(__aarch64__)
++# define TRY_EMPTY_VM_SPACE	0x1000000000
+ #elif defined(__ARM_EABI__)
+ # define TRY_EMPTY_VM_SPACE     0x60000000
+ #elif defined(__mips__) && defined(__LP64__)

                 reply	other threads:[~2026-06-29 12:26 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=178273596532.1.15526906242053771014.rpms-gcc-39f49505ef60@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