Tero, I think I have what I need, thank you.
It would be nice though if the OpenBSD port worked, and if the patches were in 
mainline gcc.
I'm running 4.3 now, but that doesn't fix it.
I took what I needed of the patches, submitted those to our cvs, and code to 
apply them at build time.
I only need the backend, not any front end. This is for Modula-3.
 
Also, all those changes of 0 to NULL, those aren't really needed, are they?I 
understand that IF 0 is defined simply as 0, which is legal, and there is 
varargs, and pointer is bigger than int, such as most 64 bit systems, and you 
want a null pointer, you won't likely get it.
However this seems like a stretch. In C, NULL is likely at least ((void*)0) 
already, or in C++ at least 0L instead of plain 0.
Or even some compiler builtin __null, though I don't think that is necessary.
Granted, if #define NULL 0, then a change would be needed. I'd also have to 
check if NULL can be any integral type, or if the standard mandates it is the 
size of a pointer. It's possible #define NULL 0 on a 64 bit system with 32 bit 
int is not standard-legal.
 
Thanks.
 
 - Jay> Date: Mon, 9 Jun 2008 17:56:18 +0300> From: [EMAIL PROTECTED]> To: 
[EMAIL PROTECTED]> CC: ports@openbsd.org> Subject: Re: gcc 4.3 on OpenBSD?> > 
On Tue, 20 May 2008 20:50:58 +0000 Jay wrote:> > > The gcc 4.3 port is mildly 
broken, right? At least on OpenBSD 4.2?> > I'll upgrade to OpenBSD 4.3 soon. 
Actually I have OpenBSD 4.2 on one machine and OpenBSD 4.3 on another and I 
think broken on both but I have to check.> > I have partially working gcc 4.3.0 
port at> 
http://gnuada.svn.sourceforge.net/viewvc/gnuada/trunk/OpenBSD/current/lang/gcc/4.3/>
 > While the URL says "current" I have actually tested the port only on> 
OpenBSD 4.3-release.> > Partially working means that the port is not pretty, 
but produces> a working executable on i386 platform with C and Ada frontends.> 
I haven't really tested the C frontend, but the Ada frontend can> compile 
things like AWS and Polyorb from Adacore Subversion repository.> > -- > Tero 
Koskinen <[EMAIL PROTECTED]>

Reply via email to