[Info-vax] GCC for VMS, was: Re: fortran compiler roadmap?
Simon Clubley
clubley at remove_me.eisner.decus.org-Earth.UFP
Tue Apr 30 07:59:14 EDT 2013
On 2013-04-30, Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP> wrote:
> On 2013-04-29, Craig A. Berry <craigberry at mac.com.invalid> wrote:
>> In article <klmspl$j63$1 at dont-email.me>,
>> Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP> wrote:
>>
>>> That makes the DEC C headers incompatible with gcc when you have, for
>>> example, pointers in structs and want to use that struct with existing
>>> functions in the DEC C RTL.
>>
>> I'm pretty sure the same or similar headers worked with Tru64. Of
>> course, regardless of platform, DEC C can do either 32-bit or 64-bit
>> pointers according to what you tell it. Not sure if gcc can do that.
>>
>
> The basic problem is that you need to interact with a existing decc$shr.exe
> binary which has been built in a specific way. What you can do is to set
> the header definitions in such a way to force the calling of one of
> the other variants of stat():
>
Ok, change of plan. :-)
I've just had a quick look at the gcc head to see if gcc has had any
more support for DEC C specific pragmas added recently and it turns out
that variable sized pointer support was checked into gcc about a year
ago but it appears to have only been pushed to the gcc 4.8 branch.
I am using gcc 4.7.3, which was released about 3 weeks ago (and hence
is more recent than gcc 4.8), but it does not have that variable sized
pointer support in it.
I'm amazed at just how recent this stuff is; gcc 4.8 was only released
at the end of March, so if I had playing with VMS cross compilers a couple
of months ago, my only option would have been the path I was about to
take.
(And no, I would not have been about to start playing with the head
version of the code, given the size and complexity of gcc.)
So now, I get to play with a .0 release of a gcc compiler released just
over a month ago with major chunks of it rewritten in C++ for this
release (and hence needs a C++ compiler to now build it) and to build it
for a target which is not one of the mainstream gcc targets. Wonderful. :-)
I'll come back when I have something to report. :-)
Simon.
--
Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980s technology to a 21st century world
More information about the Info-vax
mailing list