Related articles |
---|
Port of GCC to Intel IA-64 architecture (Merced) jpripp@ecsu.campus.mci.net (Jason Tripp) (1998-06-27) |
Re: Port of GCC to Intel IA-64 architecture (Merced) Alexandru.Petrescu@crpht.lu (Alexandru Petrescu) (1998-06-28) |
Re: Port of GCC to Intel IA-64 architecture (Merced) fjh@cs.mu.OZ.AU (1998-06-28) |
Re: Port of GCC to Intel IA-64 architecture (Merced) sef@kithrup.com (Sean Eric Fagan) (1998-07-01) |
Re: Port of GCC to Intel IA-64 architecture (Merced) burley@cygnus.com (Craig Burley) (1998-07-01) |
Re: Port of GCC to Intel IA-64 architecture (Merced) meissner@cygnus.com (Michael Meissner) (1998-07-01) |
Re: Port of GCC to Intel IA-64 architecture (Merced) tim@wagner.princeton.edu (1998-07-08) |
Re: Port of GCC to Intel IA-64 architecture (Merced) fjh@cs.mu.OZ.AU (1998-07-10) |
From: | tim@wagner.princeton.edu |
Newsgroups: | comp.compilers |
Date: | 8 Jul 1998 01:38:20 -0400 |
Organization: | Chemistry Department, Princeton University |
References: | 98-06-153 98-06-158 98-06-166 98-07-014 |
Keywords: | GCC, architecture |
Craig Burley <burley@cygnus.com> writes:
> What is still a problem, AFAIK, is that, internally, gcc makes some
> assumptions about the equivalency of sizes of integers between the
> host and target machines.
What is even worse, IMO, is that gcc will not warn about casting a pointer
to an integer *unless* you are on a machine where the sizes are different.
When I was maintaining a program that was (painfully) being moved
alphas back when they were new, this was very annoying, since I had to
rely on other people's compile logs instead of just using something
like -Wpointer-integer.
---------------------------------------------------------------------------
Tim Hollebeek
email: tim@wfn-shop.princeton.edu
URL: http://wfn-shop.princeton.edu/~tim
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.