public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Philip Blundell <Philip.Blundell@pobox.com>
To: libc-hacker@sources.redhat.com
Subject: fix a compile error on arm
Date: Thu, 22 Apr 2004 07:25:00 -0000	[thread overview]
Message-ID: <1082618661.29708.50.camel@dixie.nexus.co.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 78 bytes --]

This patch removes INTUSE() from some calls to _dl_signal_error.

Thanks

p.


[-- Attachment #2: intuse.patch --]
[-- Type: text/x-patch, Size: 1240 bytes --]

2004-04-22  Philip Blundell  <philb@gnu.org>

	* sysdeps/arm/dl-machine.h (elf_machine_rela): Don't use INTUSE
	when calling _dl_signal_error.
	(elf_machine_rel): Likewise.

Index: sysdeps/arm/dl-machine.h
===================================================================
RCS file: /cvs/glibc/libc/sysdeps/arm/dl-machine.h,v
retrieving revision 1.46
diff -u -r1.46 dl-machine.h
--- sysdeps/arm/dl-machine.h	5 Mar 2004 10:21:30 -0000	1.46
+++ sysdeps/arm/dl-machine.h	22 Apr 2004 06:39:24 -0000
@@ -507,9 +505,8 @@
 		 topbits = newvalue & 0xfe000000;
 		 if (topbits != 0xfe000000 && topbits != 0x00000000)
 		   {
-		     INTUSE (_dl_signal_error)
-		       (0, map->l_name, NULL,
-			"R_ARM_PC24 relocation out of range");
+		     _dl_signal_error (0, map->l_name, NULL,
+				       "R_ARM_PC24 relocation out of range");
 		   }
 	       }
 	     newvalue >>= 2;
@@ -588,9 +585,8 @@
 		 topbits = newvalue & 0xfe000000;
 		 if (topbits != 0xfe000000 && topbits != 0x00000000)
 		   {
-		     INTUSE (_dl_signal_error)
-		       (0, map->l_name, NULL,
-			"R_ARM_PC24 relocation out of range");
+		     _dl_signal_error (0, map->l_name, NULL,
+				       "R_ARM_PC24 relocation out of range");
 		   }
 	       }
 	     newvalue >>= 2;

             reply	other threads:[~2004-04-22  7:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22  7:25 Philip Blundell [this message]
2004-04-22  7:32 ` Ulrich Drepper

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=1082618661.29708.50.camel@dixie.nexus.co.uk \
    --to=philip.blundell@pobox.com \
    --cc=libc-hacker@sources.redhat.com \
    /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).