From: Clive Nicolson <srwmcln@baby.bedroom.gen.nz>
To: egcs@cygnus.com
Subject: Re: front end interface
Date: Mon, 18 Aug 1997 10:42:06 -0000 [thread overview]
Message-ID: <199708180820.KAA19291@radagast.iuk.tu-harburg.de> (raw)
Message-ID: <19970818104206.ZfkMn5RAOfL0dpIpf1ggO5EQf45lqlICxB-VVIcnyYQ@z> (raw)
In-Reply-To: front end interface
>> I've mentioned this in private email but I should let the list know as
>> well: my alias code in the back end recognizes certain C function names.
>> I believe this is correct because all languages will be linking with the C
>> library and must mangle or prohibit any names which conflict. For example,
>> Fortran symbols traditionally have a "_" added to the end.
>>
>If I understand this correctly, you're depending on memcpy() being named 'memcpy' ?!
>
>This leads into trouble with the current openVMS ports (vax and alpha), where most
>library functions are '#define'd with a DECC$ in front (and others have a __asm() appended
>to their declaration). So the compiler doesn't see memcpy but DECC$MEMCPY.
This is somewhat in violation of the ANSI C rules about names. I have a patched version
of gcc 2.7.1 (vax vms) that translates ANSI C names (to those found in the DEC
runtime libraries) in the assembler, this is much like that done by DEC's DECC compiler.
I still have to fix the passing of some attributes via the name prefixing hack used by
gcc vax/vms.
Clive.
next reply other threads:[~1997-08-18 10:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-18 8:22 Thomas Hiller [this message]
1997-08-18 9:11 ` GCC Projects? Bernd Schmidt
1997-08-18 9:11 ` prototyping Andi Kleen
1997-08-18 9:11 ` Will egcs support MachTen? N8TM
1997-08-18 10:42 ` front end interface Clive Nicolson
1997-08-18 13:29 ` [EGCS] Re: double alignment patch for x86 Dave Love
1997-08-18 18:22 prototyping Per Bothner
1997-08-18 18:22 ` 2 (small?) problems Jim Meyering
1997-08-18 18:22 Fergus Henderson
1997-08-19 2:36 Ian Lance Taylor
1997-08-25 23:43 Jim Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199708180820.KAA19291@radagast.iuk.tu-harburg.de \
--to=srwmcln@baby.bedroom.gen.nz \
--cc=egcs@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).