Subject: | |
From: | |
Reply To: | |
Date: | Wed, 16 Dec 1998 16:16:03 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Stan writes:
>But...wait...what's that CSEQ is telling us? (You *do have* CSEQ don't you?)
..
>Did I mention that I'd never try to call an intrinsic from gcc without
>using CSEQ first? :)
For anyone trying to use gcc and intrinsics, CSEQ is a must have! In fact,
(I hope I'm not announcing things out of order, here ...) CSEQ will
generate gcc calls that take advantage of my longpointer wrappers:
CSEQ [nm]: set gcc
ok
Option settings:
C : reset
EXTRAS : SET
EXTRASONLY : reset
GCC : SET
LANGuage : reset
MACro : reset
NM : SET
PARMS : SET
PARMTRUNC : SET
PE : reset
SORT : SET
UNNAMED : reset
CSEQ [nm, gcc]: fwrite
#include "/usr/contrib/intrinsics/types.h"
extern void FWRITE (
int16 filenum, /* R26 */
longpointer /* void */ target, /* (skip R25)
R23, R24 */
int16 tcount, /* SP-$0032 */
uint16 control); /* SP-$0036 */
/* CCE: ok */
/* CCG: EOF */
/* CCL: error */
/* tcount is > 0 for 16-bit words, < 0 for bytes */
/* If MR is not on, trying to write a record larger */
/* than the record size is illegal. */
CSEQ [nm, gcc]:
|
|
|