Richard D. Jackson wrote:
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.
Sure, and it's one of the programs I use most (next to ls maybe :-).
<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 ... ;-)
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.
It should not change them (apart from the initialization in lang.c which I suppose is dropped now).
I don't see how the int->char change should be a problem, either, but I don't know exactly ...
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.
OK, I guess then Waldek or I will deal with the issue when we get to it (I probably won't try it until the release of a new GCC version).
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 :
- work on the documentation as there are quite a few holes in it.
Indeed (in some areas the holes are bigger than the rest ;-).
- write some of the missing utilites ( A automake like tool for gpc,
I'm working on it (this is, when I'm not busy with GPC bugs etc.). Much of it is finished, but a few substantial problems are left. Probably not a good starter project since there would be some learning of the internals of the utility first ...
a source code beutifier,
Eike Lange and Thorsten Hindermann wrote a tool (pindent) some time ago, but I don't know if it has been updated to conform with the GPC Coding Standards.
a documentation tool )
(See my other mail.)
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 ).
I know -- the only way many things are documented are in the interface of the GPC unit (if you don't want to go into the implementation which is often quite low-level).
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.
BTW, there is a separate list for documentation issues gpc-doc@gnu.de since probably not all readers of this list are interested in those patches.
Frank