public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robert Zitoun <zitoun@lapp.in2p3.fr>
To: help-gcc@gnu.org
Subject: How can I force long words to be 32 bits on DEC-ALPHA ?
Date: Wed, 16 Feb 2000 10:31:00 -0000	[thread overview]
Message-ID: <38AAED04.393536C8@lapp.in2p3.fr> (raw)

I have a C-program running on HP in which there are a lot of "unsigned
long*" pointers.
I try to port this program to DEC-ALPHA, but here,  Unsigned long
pointers point to 64 bit words.

Is there any way to force the compiler to understand "long" as 32 bit on
any machine ? (DEC ALPHA especially)

                             Thank you for your help

                                                   Robert

WARNING: multiple messages have this Message-ID
From: Robert Zitoun <zitoun@lapp.in2p3.fr>
To: help-gcc@gnu.org
Subject: How can I force long words to be 32 bits on DEC-ALPHA ?
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <38AAED04.393536C8@lapp.in2p3.fr> (raw)
Message-ID: <20000401000000.gEtH-XPGgM18C5N9DvZbPCp6utaifDClUiiRP-WCeCc@z> (raw)

I have a C-program running on HP in which there are a lot of "unsigned
long*" pointers.
I try to port this program to DEC-ALPHA, but here,  Unsigned long
pointers point to 64 bit words.

Is there any way to force the compiler to understand "long" as 32 bit on
any machine ? (DEC ALPHA especially)

                             Thank you for your help

                                                   Robert

             reply	other threads:[~2000-02-16 10:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-16 10:31 Robert Zitoun [this message]
2000-02-16 16:49 ` Bill C Riemers
2000-04-01  0:00   ` Bill C Riemers
2000-04-01  0:00 ` Robert Zitoun

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=38AAED04.393536C8@lapp.in2p3.fr \
    --to=zitoun@lapp.in2p3.fr \
    --cc=help-gcc@gnu.org \
    /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).