[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GCC 3.3 on AlphaVMS under GNV

From: Bernard Giroud
Subject: Re: GCC 3.3 on AlphaVMS under GNV
Date: Fri, 27 Feb 2004 16:21:46 +0100

Hi all,

I'm in the process of building a GCC C compiler version 3.3
on OpenVMS Alpha under GNV.

I hit two real problems so far:

1) the compiler emits named ".section" directives which are
   not accepted by gas 2.13.91 (seems to be only for elf).
   AFAICS this behavior is not changed in current CVS.
   Did I miss some point ? Is this target only for elf ?
  I'm willing to do the change in the EVAX model for gas,
  if it is the right way to go ? What is the history on VMS
   modifications ?

2) The compiler bumps when trying to compile _muldi3:
   it seems related to __asm__ and output operand. This
   is the smaller code which induces the abort:

CHROME::BG>type t.i
int main(int argc, char **argv) {int i = 5;
   __asm__ ("umulh %r1":"=r"(i):);
CHROME::BG>mc sys$disk:[]cc1 -fpreprocessed t.i  -quiet -version -o t.s
GNU C version 3.3 20030429 (prerelease) (OpenVMS/Alpha) compiled by CC.
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
t.i: In function `main':
t.i:2: internal compiler error: Bus error

   Here also before I start debugging the compiler, has anyone
already hit that problem ?

Best regards,

Bernard Giroud
Credit Lyonnais (Suisse) SA
----- Original Message -----
From: "Douglas B Rupp" <address@hidden>
To: "Bernard Giroud" <address@hidden>
Sent: Wednesday, February 11, 2004 7:05 AM
Subject: Re: GCC 3.3 on AlphaVMS under GNV

Attention : ce message provient de l'extérieur du Groupe CL.
S'il possède un caractère bancaire, veuillez, S.V.P., le traiter
de la meme manière qu'un fax entrant.

We don't do much with Gnu C. We maintain it only so that we can bootstrap
and compile the few "C" parts of GNAT (Gnu Ada) on VMS..  If your only
interest is in "C", you are much better off sticking with DEC C.

> What is the current status ?
I'm baselined on gcc-3.2.3  but occasionally build using head sources.
Currently there's a problem with the new autoconf requirement on the head.
> How did you build it ?
$ bash -c ".../configure ..."
$ bash -c "make ..."
> Did you try under GNV or under DCL ?
Neither. I have my own set of Gnu tools.
> How did you solve the problem of the variable readonly in varasm.c ?
> Are you the author of the FILE_TYPE_OVERLOADED #ifdef in system.h ?
> If not (I don't remember how I got it!), how did you solve the problem
> of compiling with a standard stdio.h form hp with the macro FILE_TYPE ?
It sounds like you are trying to build with DEC C?  I haven't done that in
> How was pexecute running with fork (vfork?) ?
#define fork vfork

This e-mail contains confidential information or information belonging 
to the Credit Lyonnais Group entity sending it and is intended solely 
for the addressees. Any views expressed in this message are those of 
the individual sender and its contents do not constitute a commitment 
by Credit Lyonnais unless confirmed by letter or fax. The unauthorised 
disclosure, use, dissemination or copying (either whole or partial) of 
this e-mail, or any information it contains, is prohibited. E-mails are 
susceptible to alteration and their integrity cannot be guaranteed.
Internet communications are not secured and therefore Credit Lyonnais 
shall not be liable for this e-mail if modified or falsified. If you 
are not the intended recipient of this e-mail, please delete it 
immediately from your system and notify the sender of the wrong 
delivery and the mail deletion.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]