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.1.1-2
Date: Mon, 29 Jun 2026 12:29:50 GMT	[thread overview]
Message-ID: <178273619044.1.14488896312808552243.rpms-gcc-b2315f360e31@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/gcc
Branch : rhel-f41-base
Commit : b2315f360e31631b87e283ddfb11a9b4365e3117
Author : Jakub Jelinek <jakub@redhat.com>
Date   : 2022-06-28T21:07:05+02:00
Stats  : +31/-0 in 2 file(s)
URL    : https://src.fedoraproject.org/rpms/gcc/c/b2315f360e31631b87e283ddfb11a9b4365e3117?branch=rhel-f41-base

Log:
12.1.1-2

---
diff --git a/gcc.spec b/gcc.spec
index 910f7fe..1bc47d5 100644
--- a/gcc.spec
+++ b/gcc.spec
@@ -275,6 +275,7 @@ Patch8: gcc12-no-add-needed.patch
 Patch9: gcc12-Wno-format-security.patch
 Patch10: gcc12-rh1574936.patch
 Patch11: gcc12-d-shared-libphobos.patch
+Patch12: gcc12-pr105551.patch
 
 Patch100: gcc12-fortran-fdec-duplicates.patch
 Patch101: gcc12-fortran-flogical-as-integer.patch
@@ -802,6 +803,7 @@ so that there cannot be any synchronization problems.
 %patch10 -p0 -b .rh1574936~
 %endif
 %patch11 -p0 -b .d-shared-libphobos~
+%patch12 -p0 -b .pr105551~
 
 %if 0%{?rhel} >= 9
 %patch100 -p1 -b .fortran-fdec-duplicates~
@@ -3238,6 +3240,7 @@ end
 	tree-optimization/105940
 - enable tsan and lsan on s390x (#2101610)
 - trim RHEL fortran patches
+- fix nvptx build (PRs bootstrap/105551, target/105938)
 
 * Sat May  7 2022 Jakub Jelinek <jakub@redhat.com> 12.1.1-1
 - update from releases/gcc-12 branch

diff --git a/gcc12-pr105551.patch b/gcc12-pr105551.patch
new file mode 100644
index 0000000..ce8be26
--- /dev/null
+++ b/gcc12-pr105551.patch
@@ -0,0 +1,28 @@
+2022-05-11  Richard Biener  <rguenther@suse.de>
+
+	PR bootstrap/105551
+	* opts.cc (finish_options): Also disable var-tracking if
+	!DWARF2_DEBUGGING_INFO.
+
+--- gcc/opts.cc
++++ gcc/opts.cc
+@@ -1334,11 +1334,15 @@ finish_options (struct gcc_options *opts, struct gcc_options *opts_set,
+ 	      || opts->x_flag_selective_scheduling2));
+ 
+   /* We know which debug output will be used so we can set flag_var_tracking
+-     and flag_var_tracking_uninit if the user has not specified them.  Note
+-     we have not yet initialized debug_hooks so we might uselessly run
+-     var-tracking on targets without var_location debug hook support.  */
++     and flag_var_tracking_uninit if the user has not specified them.  */
+   if (opts->x_debug_info_level < DINFO_LEVEL_NORMAL
+-      || !dwarf_debuginfo_p (opts))
++      || !dwarf_debuginfo_p (opts)
++      /* We have not yet initialized debug hooks so match that to check
++	 whether we're only doing DWARF2_LINENO_DEBUGGING_INFO.  */
++#ifndef DWARF2_DEBUGGING_INFO
++      || true
++#endif
++     )
+     {
+       if ((opts_set->x_flag_var_tracking && opts->x_flag_var_tracking == 1)
+ 	  || (opts_set->x_flag_var_tracking_uninit

             reply	other threads:[~2026-06-29 12:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-29 12:29 Jakub Jelinek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-06-29 12:29 [rpms/gcc] rhel-f41-base: 12.1.1-2 Jakub Jelinek
2026-06-29 12:29 Jakub Jelinek

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=178273619044.1.14488896312808552243.rpms-gcc-b2315f360e31@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