public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/gcc] rhel-f41-base: 4.3.2-1
Date: Mon, 29 Jun 2026 12:23:54 GMT [thread overview]
Message-ID: <178273583470.1.16372622736274035509.rpms-gcc-1af11d046b92@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/gcc
Branch : rhel-f41-base
Commit : 1af11d046b923cd4daeb16bc2390f2b499d5e73c
Author : Jakub Jelinek <jakub@fedoraproject.org>
Date : 2008-08-29T16:55:52+00:00
Stats : +3/-2 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/gcc/c/1af11d046b923cd4daeb16bc2390f2b499d5e73c?branch=rhel-f41-base
Log:
4.3.2-1
---
diff --git a/gcc43-fortran-debug10.patch b/gcc43-fortran-debug10.patch
index d446519..7f93659 100644
--- a/gcc43-fortran-debug10.patch
+++ b/gcc43-fortran-debug10.patch
@@ -371,12 +371,13 @@
/* If we don't have a copy of this variable in memory for some reason (such
as a C++ member constant that doesn't have an out-of-line definition),
we should tell the debugger about the constant value. */
-@@ -11781,6 +11940,18 @@ tree_add_const_value_attribute (dw_die_r
+@@ -11781,6 +11940,19 @@ tree_add_const_value_attribute (dw_die_r
rtl = rtl_for_decl_init (init, type);
if (rtl)
add_const_value_attribute (var_die, rtl);
+ /* If the host and target are sane, try harder. */
-+ else if (CHAR_BIT == 8 && BITS_PER_UNIT == 8)
++ else if (CHAR_BIT == 8 && BITS_PER_UNIT == 8
++ && initializer_constant_valid_p (init, type))
+ {
+ HOST_WIDE_INT size = int_size_in_bytes (TREE_TYPE (init));
+ if (size > 0 && (int) size == size)
next reply other threads:[~2026-06-29 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 12:23 Jakub Jelinek [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-29 12:23 [rpms/gcc] rhel-f41-base: 4.3.2-1 Jakub Jelinek
2026-06-29 12:23 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=178273583470.1.16372622736274035509.rpms-gcc-1af11d046b92@fedoraproject.org \
--to=jakub@fedoraproject.org \
--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