public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: "Moore, Mathew L" <MooreML@BATTELLE.ORG>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Avoiding "assignment from incompatible pointer type" warning
Date: Mon, 21 Oct 2002 07:17:00 -0000	[thread overview]
Message-ID: <87adl7vpuc.fsf@deneb.enyo.de> (raw)
In-Reply-To: <2F05A390F72A0A409390E016D23E45E8042DBEB6@ns-bco-mse4.im.battelle.org> ("Moore, Mathew L"'s message of "Mon, 21 Oct 2002 10:04:01 -0400")

"Moore, Mathew L" <MooreML@BATTELLE.ORG> writes:

> To help expand my (very) limited knowledge, does this mean that 
>
> 	float f;
> 	int *p = (int*)&f;
>
> may not work even if sizeof(float) == sizeof(int)?

I think so.

Alignment is defined informally as:

       3.2
       [#1] alignment
       requirement that objects of a particular type be located  on
       storage   boundaries  with  addresses  that  are  particular
       multiples of a byte address

This definition is independent of the size of the type.  Furthermore,
there's no way to determine the required alignment of a type.

  reply	other threads:[~2002-10-21 14:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-21  7:04 Moore, Mathew L
2002-10-21  7:17 ` Florian Weimer [this message]
2002-10-21  7:43   ` John Love-Jensen
  -- strict thread matches above, loose matches on Subject: below --
2002-10-21  6:07 Moore, Mathew L
2002-10-13 13:37 Moore, Mathew L
2002-10-13 15:10 ` Florian Weimer
2002-10-13  9:08 Steve Dondley
2002-10-13  9:28 ` Joshua Nye
2002-10-13  9:34   ` Steve Dondley
2002-10-13 15:09   ` Florian Weimer
2002-10-13 15:19     ` Joshua Nye
2002-10-15 11:24     ` Joshua Nye
2002-10-21  3:12       ` Florian Weimer
2002-10-21  4:22         ` Claudio Bley
2002-10-21  4:30           ` Florian Weimer
2002-10-21  6:48             ` Claudio Bley
2002-10-21  4:42           ` Sebastian Huber
2002-10-21  6:43           ` John Love-Jensen
2002-10-21  6:52             ` Florian Weimer

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=87adl7vpuc.fsf@deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=MooreML@BATTELLE.ORG \
    --cc=gcc-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).