public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: sid@sources.redhat.com
Subject: [PATCH] Fix recent build breakage in sid
Date: Fri, 23 Jun 2006 11:07:00 -0000	[thread overview]
Message-ID: <20060623110650.GC4586@networkno.de> (raw)

Hello All,

the appended patch fixes invalid use of "register" as detected by
gcc 4.1.1.


Thiemo


2006-06-23  Thiemo Seufer  <ths@mips.com>

	* tracedis.cxx (bfd_getb16, bfd_getl16, bfd_getb32, bfd_getl32):
	Remove invalid use of register specifier.
	

Index: sid/component/cgen-cpu/tracedis.cxx
===================================================================
RCS file: /cvs/src/src/sid/component/cgen-cpu/tracedis.cxx,v
retrieving revision 1.5
diff -u -p -r1.5 tracedis.cxx
--- sid/component/cgen-cpu/tracedis.cxx	28 Oct 2005 19:53:33 -0000	1.5
+++ sid/component/cgen-cpu/tracedis.cxx	23 Jun 2006 10:58:50 -0000
@@ -85,21 +85,21 @@ bfd_get_arch(bfd *abfd)
 /* Stolen from libbfd.  */
 
 extern "C" bfd_vma
-bfd_getb16 (register const void *addr)
+bfd_getb16 (const void *addr)
 {
   const bfd_byte *byteaddr = static_cast <const bfd_byte *> (addr);
   return (byteaddr[0] << 8) | byteaddr[1];
 }
 
 extern "C" bfd_vma
-bfd_getl16 (register const void *addr)
+bfd_getl16 (const void *addr)
 {
   const bfd_byte *byteaddr = static_cast <const bfd_byte *> (addr);
   return (byteaddr[1] << 8) | byteaddr[0];
 }
 
 extern "C" bfd_vma
-bfd_getb32 (register const void *addr)
+bfd_getb32 (const void *addr)
 {
   const bfd_byte *byteaddr = static_cast <const bfd_byte *> (addr);
   unsigned long v;
@@ -112,7 +112,7 @@ bfd_getb32 (register const void *addr)
 }
 
 extern "C" bfd_vma
-bfd_getl32 (register const void *addr)
+bfd_getl32 (const void *addr)
 {
   const bfd_byte *byteaddr = static_cast <const bfd_byte *> (addr);
   unsigned long v;

             reply	other threads:[~2006-06-23 11:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23 11:07 Thiemo Seufer [this message]
2006-06-23 11:18 ` Frank Ch. Eigler

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=20060623110650.GC4586@networkno.de \
    --to=ths@networkno.de \
    --cc=sid@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).