public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: jimb@redhat.com
Cc: cgen@sourceware.org, orjan.friberg@axis.com, gdb@sources.redhat.com
Subject: Re: Troubles building cris target
Date: Tue, 15 Mar 2005 23:09:00 -0000	[thread overview]
Message-ID: <200503152309.j2FN9Ut1032072@ignucius.se.axis.com> (raw)
In-Reply-To: <vt27jk8r372.fsf@zenia.home> (message from Jim Blandy on 15 Mar 2005 16:48:01 -0500)

> From: Jim Blandy <jimb@redhat.com>
> Date: 15 Mar 2005 16:48:01 -0500

> When I try to build the GDB/sim sources from sources.redhat.com CVS on
> an AMD64 Fedora Core 2 system, the build dies trying to link the
> sim/cris/run executable with the errors below.

JFTR, I built sim successfully on i686-pc-linux-gnu (FC2) with
CVS as of "Tue Mar 15 15:09:24 UTC 2005".

> This looks simple to fix, but I haven't followed it through.

CGEN bugs are simple?  Let's talk.

> gcc -DHAVE_CONFIG_H   -DWITH_DEFAULT_MODEL='"crisv32"'  -DPROFILE=1 -DWITH_PROFILE=-1   -DWITH_ALIGNMENT=NONSTRICT_ALIGNMENT   -DWITH_ENVIRONMENT=ALL_ENVIRONMENT   -DWITH_HOST_BYTE_ORDER=LITTLE_ENDIAN     -DWITH_SCACHE=16384          -I. -I/home/jimb/gdb/src/sim/cris -I../common -I/home/jimb/gdb/src/sim/cris/../common -I../../include -I/home/jimb/gdb/src/sim/cris/../../include -I../../bfd -I/home/jimb/gdb/src/sim/cris/../../bfd -I../../opcodes -I/home/jimb/gdb/src/sim/cris/../../opcodes -I../../intl -I/home/jimb/gdb/src/sim/cris/../../intl -g3 -o run \
>   nrun.o libsim.a ../../bfd/libbfd.a ../../opcodes/libopcodes.a  ../../libiberty/libiberty.a -lnsl  
> libsim.a(mloopv10f.o)(.text+0x3c2b): In function `crisv10f_engine_run_full':
> /home/jimb/gdb/src/sim/cris/semcrisv10f-switch.c:1285: undefined reference to `ADDCSI'
> libsim.a(mloopv10f.o)(.text+0x3ff2):/home/jimb/gdb/src/sim/cris/semcrisv10f-switch.c:1348: undefined reference to `SUBCSI'

Can you please test this patch?

2005-03-16  Hans-Peter Nilsson  <hp@axis.com>

	* cris/sim-main.h: Don't include cgen-ops.h.  Define ANDIF specifically.

--- sim-main.h	Fri Jan 28 05:29:00 2005
+++ /tmp/sim-main.h	Wed Mar 16 00:00:56 2005
@@ -57,8 +57,11 @@ do { \
 #include "cgen-sim.h"
 #include "cris-sim.h"
 
-/* For occurrences of ANDIF in decodev32.c.  */
-#include "cgen-ops.h"
+/* For occurrences of ANDIF in decodev32.c.  We can't '#include
+   "cgen-ops.h"' here, as that'll break the outlining of operators in
+   sim/common/cgen-utils.c.  FIXME: CGEN bug; there should be no ANDIF:s
+   in decodev32.c.  */
+#define ANDIF(x, y) ((x) && (y))
 \f
 struct cris_sim_mmapped_page {
   USI addr;

brgds, H-P

       reply	other threads:[~2005-03-15 23:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <vt27jk8r372.fsf@zenia.home>
2005-03-15 23:09 ` Hans-Peter Nilsson [this message]
2005-03-16 17:57   ` Jim Blandy
2005-03-16 18:25     ` Hans-Peter Nilsson
2005-03-24  6:20       ` Hans-Peter Nilsson
2005-03-24 12:29       ` 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=200503152309.j2FN9Ut1032072@ignucius.se.axis.com \
    --to=hans-peter.nilsson@axis.com \
    --cc=cgen@sourceware.org \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=orjan.friberg@axis.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).