From: Richard Earnshaw <rearnsha@arm.com>
To: "Vineet Sharma, Noida" <vineets@noida.hcltech.com>
Cc: gdb@sources.redhat.com, Richard.Earnshaw@arm.com
Subject: Re: Add systemc simulator with gdb
Date: Wed, 18 Feb 2004 14:52:00 -0000 [thread overview]
Message-ID: <200402181452.i1IEq5526448@pc960.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Wed, 18 Feb 2004 19:53:38 +0530." <1B3885BC15C7024C845AAC78314766C5036B65F3@exch-01.noida.hcltech.com>
>
> Hi All,
>
> Is there any examples who have sucessfully integrated there
> simulators in c++ or systemc with gdb?
I'm guessing that most people on this list won't even know what systemc is
[*], let alone really understand what question you are asking.
> What are the issues faced in that approach?
gdb can be used for debugging c++ and other normal programming languages.
It isn't really an HDL debugger.
>
> I found the problem of conflicting types of bfd in bfd.h and
> remote-sim.h(:67). Any idea how to overcome it?
>
> ../../include/gdb/remote-sim.h:67: conflicting types for `struct bfd'
> /usr/include/bfd.h:78: previous declaration as `typedef struct _bfd bfd'
> ../../include/gdb/remote-sim.h:108: using typedef-name `bfd' after `struct'
> ../../include/gdb/remote-sim.h:145: using typedef-name `bfd' after `struct'
> ../../include/gdb/remote-sim.h:165: using typedef-name `bfd' after `struct'
> I think its bcoz of the difference in c++/g++ and gcc handling of
> forward declaration?
>
GDB is written in C, and needs to be compiled with a C compiler. It's not
C++, and I guess that if you try and compile it with G++ you'll get error
messages much like the one above.
R.
[*] For the uninitiated, SystemC started life as a simulation class
library for C++ which enables you to use C++ in much the same way as you
would any other HDL (Hardware description language). However, by
restricting your description a suitable subset of C++ you can then
accelerate it significantly with special simulators and even run hardware
synthesis tools on it. The real power comes from the fact that your test
benches can be written in abstract C++ and can then interact with your
hardware description directly.
next prev parent reply other threads:[~2004-02-18 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 14:19 Vineet Sharma, Noida
2004-02-18 14:52 ` Richard Earnshaw [this message]
2004-02-20 16:52 ` Andrew Cagney
2004-02-20 2:18 Yorkwar
2004-02-20 10:41 ` Richard Earnshaw
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=200402181452.i1IEq5526448@pc960.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb@sources.redhat.com \
--cc=vineets@noida.hcltech.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