Re: Add systemc simulator with gdb

Re: Add systemc simulator with gdb

[Yorkwar]

>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.

It will be a great improvement to integrate a SystemC or HDL simulator in GDB.
However, is there any reference about how to implement the library or bridge
to compoment written in SystemC or HDL?

Best regards.

Re: Add systemc simulator with gdb

[Richard Earnshaw]

> 
> >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.
> 
> It will be a great improvement to integrate a SystemC or HDL simulator in GDB.
> However, is there any reference about how to implement the library or bridge
> to compoment written in SystemC or HDL?
> 

I'm not aware of any work being done in this area.

R.

Re: Add systemc simulator with gdb

[Andrew Cagney]

> Hi All,
>  
> 	Is there any examples who have sucessfully integrated there
> simulators in c++ or systemc with gdb?
> 	What are the issues faced in that approach?
> 
> 	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'

FYI, it should not be including that version of bfd.h (but I don't know 
if fixing that will help much).

Andrew

> ../../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?
> 
> Your comments and inputs would be very helpfull
> 
> 
> 

Re: Add systemc simulator with gdb

[Richard Earnshaw]

> 
> 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.

Add systemc simulator with gdb

[Vineet Sharma, Noida]

Hi All,
 
	Is there any examples who have sucessfully integrated there
simulators in c++ or systemc with gdb?
	What are the issues faced in that approach?

	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?

Your comments and inputs would be very helpfull



Regards
Vineet