Anyone doing anything???
I will be too busy until after the weekend...
Monday/Tuesday I will continue where I left off.
Jan

Jan Knepper wrote:

> Anyone doing anything???
> I will be too busy until after the weekend...
> Monday/Tuesday I will continue where I left off.

Talking to me or Jonathon?  My port is now compiling and using a little GC I wrote.  It's type-aggressive, so it's faster at scanning and could do block allocation for class instances.

Nothing to be proud of, it's the minimum I can do in the minimum of time.  A full-blown D-specific GC's going to be a pretty meaty creature.  But doing this and ironing out any problems now will be a good step towards getting there.

Actually, I was talking to any one involved in the GLUE layer for the D front-end to GCC back-end, but I appreciate your response.

Did you also run into the problem with the /* */ comments broken over more than one line like:

/*******************
 *
 *
 */

The D front-end would error on the * on the second line. This construction however is being used in phobos quite a few times, so I guess the D front-end should parse it.

Jan



Burton Radons wrote:

> Jan Knepper wrote:
>
> > Anyone doing anything???
> > I will be too busy until after the weekend...
> > Monday/Tuesday I will continue where I left off.
>
> Talking to me or Jonathon?  My port is now compiling and using a little GC I wrote.  It's type-aggressive, so it's faster at scanning and could do block allocation for class instances.
>
> Nothing to be proud of, it's the minimum I can do in the minimum of
> time.  A full-blown D-specific GC's going to be a pretty meaty creature.
>   But doing this and ironing out any problems now will be a good step
> towards getting there.

I've made no progress as of yet.  I'm closing a deal.  This weekend my goal is to get it to create an executable... From there I'll start looking at what needs to be done from a lower level.

I'm really open to as much direction from you as possible on this.  I think you're knowledge and experience in this area should take the lead.

-Andy

Jan Knepper wrote:
> Actually, I was talking to any one involved in the GLUE layer for the D
> front-end to GCC back-end, but I appreciate your response.
> 
> Did you also run into the problem with the /* */ comments broken over more
> than one line like:
> 
> /*******************
>  *
>  *
>  */
> 
> The D front-end would error on the * on the second line. This construction
> however is being used in phobos quite a few times, so I guess the D
> front-end should parse it.
> 
> Jan
> 
> 
> 
> Burton Radons wrote:
> 
> 
>>Jan Knepper wrote:
>>
>>
>>>Anyone doing anything???
>>>I will be too busy until after the weekend...
>>>Monday/Tuesday I will continue where I left off.
>>
>>Talking to me or Jonathon?  My port is now compiling and using a little
>>GC I wrote.  It's type-aggressive, so it's faster at scanning and could
>>do block allocation for class instances.
>>
>>Nothing to be proud of, it's the minimum I can do in the minimum of
>>time.  A full-blown D-specific GC's going to be a pretty meaty creature.
>>  But doing this and ironing out any problems now will be a good step
>>towards getting there.
> 
> 

"Andrew C. Oliver" wrote:

> I've made no progress as of yet.  I'm closing a deal.  This weekend my goal is to get it to create an executable... From there I'll start looking at what needs to be done from a lower level.

OK. Well, getting the build process integrated into the gcc build would be cool.

> I'm really open to as much direction from you as possible on this.  I think you're knowledge and experience in this area should take the lead.

Thanks, but it has been over 10 years since I wrote my C++ to C converter and
over 13 years I wrote a compiler.
Next week I will be getting into the GCC stuff in more detail to see how I can
hook the two up.

Jan



>
>
> -Andy
>
> Jan Knepper wrote:
> > Actually, I was talking to any one involved in the GLUE layer for the D front-end to GCC back-end, but I appreciate your response.
> >
> > Did you also run into the problem with the /* */ comments broken over more than one line like:
> >
> > /*******************
> >  *
> >  *
> >  */
> >
> > The D front-end would error on the * on the second line. This construction however is being used in phobos quite a few times, so I guess the D front-end should parse it.
> >
> > Jan
> >
> >
> >
> > Burton Radons wrote:
> >
> >
> >>Jan Knepper wrote:
> >>
> >>
> >>>Anyone doing anything???
> >>>I will be too busy until after the weekend...
> >>>Monday/Tuesday I will continue where I left off.
> >>
> >>Talking to me or Jonathon?  My port is now compiling and using a little GC I wrote.  It's type-aggressive, so it's faster at scanning and could do block allocation for class instances.
> >>
> >>Nothing to be proud of, it's the minimum I can do in the minimum of time.  A full-blown D-specific GC's going to be a pretty meaty creature.
> >>  But doing this and ironing out any problems now will be a good step
> >>towards getting there.
> >
> >

Jan Knepper wrote:
> "Andrew C. Oliver" wrote:
> 
> 
>>I've made no progress as of yet.  I'm closing a deal.  This weekend my
>>goal is to get it to create an executable... From there I'll start
>>looking at what needs to be done from a lower level.
> 
> 
> OK. Well, getting the build process integrated into the gcc build would be cool.
> 

Yes.  I got it to *build*.... and theoretically it worked together. Just nothing really resulted from it...

> 
>>I'm really open to as much direction from you as possible on this.  I think
>>you're knowledge and experience in this area should take the lead.
> 
> 
> Thanks, but it has been over 10 years since I wrote my C++ to C converter and
> over 13 years I wrote a compiler.
> Next week I will be getting into the GCC stuff in more detail to see how I can
> hook the two up.
> 

And its been like 3-4 years since my last serious effort in C/C++. (Which oddly enough was an NT service...long story...involved a mainframe ;-) )


> Jan
> 
> 
> 
> 
>>
>>-Andy
>>
>>Jan Knepper wrote:
>>
>>>Actually, I was talking to any one involved in the GLUE layer for the D
>>>front-end to GCC back-end, but I appreciate your response.
>>>
>>>Did you also run into the problem with the /* */ comments broken over more
>>>than one line like:
>>>
>>>/*******************
>>> *
>>> *
>>> */
>>>
>>>The D front-end would error on the * on the second line. This construction
>>>however is being used in phobos quite a few times, so I guess the D
>>>front-end should parse it.
>>>
>>>Jan
>>>
>>>
>>>
>>>Burton Radons wrote:
>>>
>>>
>>>
>>>>Jan Knepper wrote:
>>>>
>>>>
>>>>
>>>>>Anyone doing anything???
>>>>>I will be too busy until after the weekend...
>>>>>Monday/Tuesday I will continue where I left off.
>>>>
>>>>Talking to me or Jonathon?  My port is now compiling and using a little
>>>>GC I wrote.  It's type-aggressive, so it's faster at scanning and could
>>>>do block allocation for class instances.
>>>>
>>>>Nothing to be proud of, it's the minimum I can do in the minimum of
>>>>time.  A full-blown D-specific GC's going to be a pretty meaty creature.
>>>> But doing this and ironing out any problems now will be a good step
>>>>towards getting there.
>>>
>>>
> 

> > OK. Well, getting the build process integrated into the gcc build would be cool.
> Yes.  I got it to *build*.... and theoretically it worked together. Just nothing really resulted from it...

So, if I understand you well you already got the .in files done? If so: Cool!

> > Thanks, but it has been over 10 years since I wrote my C++ to C converter and
> > over 13 years I wrote a compiler.
> > Next week I will be getting into the GCC stuff in more detail to see how I can
> > hook the two up.
> And its been like 3-4 years since my last serious effort in C/C++.
> (Which oddly enough was an NT service...long story...involved a
> mainframe ;-) )

That has been about 1 second for me I guess... <g>
I guess I have been using C++ for too long by now... <g>

Jan

On Fri, 02 Aug 2002 10:36:34 -0400 Jan Knepper <jan@smartsoft.cc> wrote:

> Did you also run into the problem with the /* */ comments broken over more than one line like:
> 
> /*******************
>  *
>  *
>  */
> 
> The D front-end would error on the * on the second line. This construction however is being used in phobos quite a few times, so I guess the D front-end should parse it.

It's an old DMD bug. I don't remember the exact reason (which I've figured out when I first came over it), but sometimes it complains on such comments, sometimes it isn't - I have such a comment in WinD and it works fine. It has something to do with whitespace as far as I remember.

Pavel Minayev wrote:

> On Fri, 02 Aug 2002 10:36:34 -0400 Jan Knepper <jan@smartsoft.cc> wrote:
>
> > Did you also run into the problem with the /* */ comments broken over more than one line like:
> >
> > /*******************
> >  *
> >  *
> >  */
> >
> > The D front-end would error on the * on the second line. This construction however is being used in phobos quite a few times, so I guess the D front-end should parse it.
>
> It's an old DMD bug. I don't remember the exact reason (which I've figured out when I first came over it), but sometimes it complains on such comments, sometimes it isn't - I have such a comment in WinD and it works fine. It has something to do with whitespace as far as I remember.

No, it has something to do with line counting and and end of line not being processed properly. (I think). I fixed it in the D front-end which is available.

Jan

Jan Knepper wrote:
> Anyone doing anything???
> I will be too busy until after the weekend...
> Monday/Tuesday I will continue where I left off.
> Jan
> 

I'm trying to figure out the gcc stuff, For the sake of interfacing,
it might be interesting to output whatever the D front end uses as
an intermediary representation to a file.

-Jon