public inbox for binutils-cvs@sourceware.org
help / color / mirror / Atom feed
From: Nick Clifton <nickc@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] Fix indentation in loongarch code, preventing a compile time warning.
Date: Tue, 26 Jul 2022 10:34:15 +0000 (GMT)	[thread overview]
Message-ID: <20220726103415.7429C385801B@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=27121f6740fa2051609b2d781d77c4cd23aa590b

commit 27121f6740fa2051609b2d781d77c4cd23aa590b
Author: Nick Clifton <nickc@redhat.com>
Date:   Tue Jul 26 11:33:51 2022 +0100

    Fix indentation in loongarch code, preventing a compile time warning.

Diff:
---
 bfd/ChangeLog         |  5 +++++
 bfd/elfnn-loongarch.c | 22 ++++++++++------------
 2 files changed, 15 insertions(+), 12 deletions(-)

diff --git a/bfd/ChangeLog b/bfd/ChangeLog
index b88f33b5e72..acbb8f9e817 100644
--- a/bfd/ChangeLog
+++ b/bfd/ChangeLog
@@ -1,3 +1,8 @@
+2022-07-26  Nick Clifton  <nickc@redhat.com>
+
+	* elfnn-loongarch.c (loongarch_elf_relocate_section): Fix
+	indentation.
+
 2022-07-08  Nick Clifton  <nickc@redhat.com>
 
 	* 2.39 branch created.
diff --git a/bfd/elfnn-loongarch.c b/bfd/elfnn-loongarch.c
index 4efe3d9370c..99d889ae11d 100644
--- a/bfd/elfnn-loongarch.c
+++ b/bfd/elfnn-loongarch.c
@@ -3089,19 +3089,17 @@ loongarch_elf_relocate_section (bfd *output_bfd, struct bfd_link_info *info,
 	  else
 	    relocation += rel->r_addend;
 
+	  relocation &= 0xfff;
+	  /* Signed extend.  */
+	  relocation = (relocation ^ 0x800) - 0x800;
+
+	  /* For 2G jump, generate pcalau12i, jirl.  */
+	  /* If use jirl, turns to R_LARCH_B16.  */
+	  uint32_t insn = bfd_get (32, input_bfd, contents + rel->r_offset);
+	  if ((insn & 0x4c000000) == 0x4c000000)
 	    {
-	      relocation &= 0xfff;
-	      /* Signed extend.  */
-	      relocation = (relocation ^ 0x800) - 0x800;
-
-	      /* For 2G jump, generate pcalau12i, jirl.  */
-	      /* If use jirl, turns to R_LARCH_B16.  */
-	      uint32_t insn = bfd_get (32, input_bfd, contents + rel->r_offset);
-	      if ((insn & 0x4c000000) == 0x4c000000)
-		{
-		  rel->r_info = ELFNN_R_INFO (r_symndx, R_LARCH_B16);
-		  howto = loongarch_elf_rtype_to_howto (input_bfd, R_LARCH_B16);
-		}
+	      rel->r_info = ELFNN_R_INFO (r_symndx, R_LARCH_B16);
+	      howto = loongarch_elf_rtype_to_howto (input_bfd, R_LARCH_B16);
 	    }
 	  break;


                 reply	other threads:[~2022-07-26 10:34 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=20220726103415.7429C385801B@sourceware.org \
    --to=nickc@sourceware.org \
    --cc=bfd-cvs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).