Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
To: gdb-patches@sources.redhat.com
Subject: 6.1: Fix gcc 3.5.0 failure in sim
Date: Mon, 19 Apr 2004 20:55:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.55.0404192249530.18710@jurand.ds.pg.gda.pl> (raw)

Hello,

 Building sim for mipsel-linux fails with gcc 3.5.0 with an "invalid
lvalue in assignment" error.  Here's a fix.

2004-04-19  Maciej W. Rozycki  <macro@ds2.pg.gda.pl>

	* mips/sim-main.h (COP0_BADVADDR): Remove a cast.

 Please apply.

  Maciej

-- 
+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+--------------------------------------------------------------+
+        e-mail: macro@ds2.pg.gda.pl, PGP key available        +

gdb-6.1-sim-gcc3.patch
diff -up --recursive --new-file gdb-6.1.macro/sim/mips/sim-main.h gdb-6.1/sim/mips/sim-main.h
--- gdb-6.1.macro/sim/mips/sim-main.h	2003-01-05 07:56:59.000000000 +0000
+++ gdb-6.1/sim/mips/sim-main.h	2004-04-15 06:53:58.000000000 +0000
@@ -383,7 +383,7 @@ struct _sim_cpu {
 #define NR_COP0_GPR	32
   unsigned_word cop0_gpr[NR_COP0_GPR];
 #define COP0_GPR	((CPU)->cop0_gpr)
-#define COP0_BADVADDR ((unsigned32)(COP0_GPR[8]))
+#define COP0_BADVADDR (COP0_GPR[8])
 
   /* While space is allocated for the floating point registers in the
      main registers array, they are stored separatly.  This is because


             reply	other threads:[~2004-04-19 20:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19 20:55 Maciej W. Rozycki [this message]
     [not found] ` <mailpost.1082408135.5083@news-sj1-1>
2004-04-19 21:02   ` cgd
2004-04-20 13:12     ` Maciej W. Rozycki
     [not found]       ` <mailpost.1082466772.363@news-sj1-1>
2004-05-12  1:59         ` cgd

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=Pine.LNX.4.55.0404192249530.18710@jurand.ds.pg.gda.pl \
    --to=macro@ds2.pg.gda.pl \
    --cc=gdb-patches@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