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: 4.9.2-1
Date: Mon, 29 Jun 2026 12:26:28 GMT	[thread overview]
Message-ID: <178273598832.1.9690037729871846048.rpms-gcc-79ac3cdb3805@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/gcc
Branch : rhel-f41-base
Commit : 79ac3cdb38051d5d82f4e7facadfc3e0d2c3e264
Author : Jakub Jelinek <jakub@redhat.com>
Date   : 2014-11-01T09:52:33+01:00
Stats  : +7/-7 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/gcc/c/79ac3cdb38051d5d82f4e7facadfc3e0d2c3e264?branch=rhel-f41-base

Log:
4.9.2-1

---
diff --git a/gcc49-pr63659.patch b/gcc49-pr63659.patch
index b4762ab..262f30b 100644
--- a/gcc49-pr63659.patch
+++ b/gcc49-pr63659.patch
@@ -8,14 +8,14 @@
 
 --- gcc/ree.c.jj	2014-10-22 15:52:18.000000000 +0200
 +++ gcc/ree.c	2014-10-27 19:18:37.287412478 +0100
-@@ -266,6 +266,50 @@ typedef struct ext_cand
+@@ -261,6 +261,50 @@ typedef struct ext_cand
  
  static int max_insn_uid;
  
 +/* Update or remove REG_EQUAL or REG_EQUIV notes for INSN.  */
 +
 +static bool
-+update_reg_equal_equiv_notes (rtx_insn *insn, enum machine_mode new_mode,
++update_reg_equal_equiv_notes (rtx insn, enum machine_mode new_mode,
 +			      enum machine_mode old_mode, enum rtx_code code)
 +{
 +  rtx *loc = &REG_NOTES (insn);
@@ -59,15 +59,15 @@
  /* Given a insn (CURR_INSN), an extension candidate for removal (CAND)
     and a pointer to the SET rtx (ORIG_SET) that needs to be modified,
     this code modifies the SET rtx to a new SET rtx that extends the
-@@ -287,6 +331,7 @@ static bool
- combine_set_extension (ext_cand *cand, rtx_insn *curr_insn, rtx *orig_set)
+@@ -282,6 +326,7 @@ static bool
+ combine_set_extension (ext_cand *cand, rtx curr_insn, rtx *orig_set)
  {
    rtx orig_src = SET_SRC (*orig_set);
 +  enum machine_mode orig_mode = GET_MODE (SET_DEST (*orig_set));
    rtx new_set;
    rtx cand_pat = PATTERN (cand->insn);
  
-@@ -323,9 +368,8 @@ combine_set_extension (ext_cand *cand, r
+@@ -318,9 +363,8 @@ combine_set_extension (ext_cand *cand, r
  	{
  	  /* Zero-extend the negative constant by masking out the bits outside
  	     the source mode.  */
@@ -78,7 +78,7 @@
  			    GET_MODE (new_reg));
  	  new_set = gen_rtx_SET (VOIDmode, new_reg, new_const_int);
  	}
-@@ -364,7 +408,9 @@ combine_set_extension (ext_cand *cand, r
+@@ -359,7 +403,9 @@ combine_set_extension (ext_cand *cand, r
  
    /* This change is a part of a group of changes.  Hence,
       validate_change will not try to commit the change.  */
@@ -89,7 +89,7 @@
      {
        if (dump_file)
          {
-@@ -414,7 +460,9 @@ transform_ifelse (ext_cand *cand, rtx_in
+@@ -409,7 +455,9 @@ transform_ifelse (ext_cand *cand, rtx de
    ifexpr = gen_rtx_IF_THEN_ELSE (cand->mode, cond, map_srcreg, map_srcreg2);
    new_set = gen_rtx_SET (VOIDmode, map_dstreg, ifexpr);
  

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-29 12:26 Jakub Jelinek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-06-29 12:26 [rpms/gcc] rhel-f41-base: 4.9.2-1 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=178273598832.1.9690037729871846048.rpms-gcc-79ac3cdb3805@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