On Sat, 2003-01-25 at 18:11, Frank Heckenbach wrote:
Richard D. Jackson wrote:
On Thu, 2003-01-23 at 08:40, Frank Heckenbach wrote:
Richard D. Jackson wrote:
<snip>
<snip>
When I first read this I thought OH man I don't even know where to start but what the heck I'll take a look :) so fired up grep and and went to work.
Well, that's how I usually start when I dive into a new area of the compiler ... ;-)
You just have to love grep one of the best tools ever created IMHO.
<snip>
I'm not sure exactly, but have you made sure that the common tree codes are put in tree_code_* the way they should be (up to now, GPC added only the Pascal specific ones, while the common ones were supplied by the backend)? More generally, that the variables are initialized the same way they are in the other languages ...
If that doesn't help, I guess it's time for gdb ... ;-)
Frank
Yes I put the common tree codes under tree_code_* in the lang.c file of the gpc front end. What I think may be the problem is that the type changed on tree_code_length from int to const unsigned char. The other two where just changed to a const which I don't think would cause a segfault but then again it may if the gpc front end is trying to change them.
Right now I don't have allot of time so I'm trying to decide what is the best use of the time I do have. There are a few things I would like to do to contribute to the gpc effort and I'm not sure that digging into the compiler code would be the best use of the time I have. Maybe later when I have more time I will do that as I find it interesting and would be a good learning experance.
Right now I'm floating these ideas on things I can do : 1) work on the documentation as there are quite a few holes in it. 2) write some more units ( file streams and a collection class are two things I would like to have for use in gpc so that would be what I would start with ) 3) write some of the missing utilites ( A automake like tool for gpc, a source code beutifier, a documentation tool )
All three of these would also have the side benifit of helping me to learn pascal. And number three will need number two. So what I may end up doing is starting with 1 by working on the areas where I have some interest then move to 2 and 3.
But I can't really start on any of them until I finish reading the documentation that is availible and get a better feel of what is needed. Like for one there is alot of things in the RTS system that is not documented ( well what I should say is that it is not documented in a way that a newbe would find easy to digest that is ).
So for the time being I'm going to spend my time reading and move from there by floating some documentation updates or changes to the list. Once I get a little more cofortable with pascal then I will tackel 2 and 3.
Richard