From: nrmj <maa1666@yahoo.fr>
To: gcc-help@gcc.gnu.org
Subject: strict aliasing and pointer to struct
Date: Tue, 11 Oct 2005 09:37:00 -0000 [thread overview]
Message-ID: <20051011093733.17209.qmail@web26908.mail.ukl.yahoo.com> (raw)
I have been googling a lot on the web about alias
analysis and strict aliasing, but haven't found much
about what is allowed or not when working with
structures.
1) If I understand the C standard correctly, the
compiler is free to assume that two pointers pointing
to different types don't alias.
If two struct have different tag name, like:
struct s1 {int i;};
struct s2 {int i;};
struct s1 *p1;
struct s2 *p2;
p1 and p2 are considered by the compiler to point
to different locations and don't alias, because p1
points to type "struct s1" and p2 points to type
"struct s2" which are different types, even if they
have the same members, right ?
2) Is it safe to cast pointer to struct B to pointer
to struct A, in order to fake inheritance, like in
this code sniplet ?
( and if it is not safe, how can I fake inheritance
? )
-------------------- myfile.c ----------------
#include <stdio.h>
#include <stdlib.h>
typedef enum { RED, BLUE, GREEN } Color;
struct Point { int x;
int y;
};
struct Color_Point { int x;
int y;
Color color;
};
struct Color_Point2{ struct Point point;
Color color;
};
int main(int argc, char* argv[])
{
struct Point* p;
struct Color_Point* my_color_point =
malloc(sizeof(struct Color_Point));
my_color_point->x = 10;
my_color_point->y = 20;
my_color_point->color = GREEN;
p = (struct Point*)my_color_point; // is it
allowed by C standard ?
printf("x:%d, y:%d\n", p->x, p->y);
struct Color_Point2* my_color_point2 =
malloc(sizeof(struct Color_Point2));
my_color_point2->point.x = 100;
my_color_point2->point.y = 200;
my_color_point2->color = RED;
p = (struct Point*)my_color_point2; // is it allowed
by C standard ?
printf("x:%d, y:%d\n", p->x, p->y);
return 0;
}
Is this example also a case of what is called
"type-punning" ?
3) When programming with socket, the following cast to
(struct sockaddr *) is very common.
But is it really safe ?
struct sockaddr_in my_addr;
...
bind(sockfd, (struct sockaddr *)&my_addr,
sizeof(struct sockaddr));
Best regards
___________________________________________________________________________
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger
Téléchargez cette version sur http://fr.messenger.yahoo.com
next reply other threads:[~2005-10-11 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 9:37 nrmj [this message]
2005-10-11 20:03 ` Ian Lance Taylor
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=20051011093733.17209.qmail@web26908.mail.ukl.yahoo.com \
--to=maa1666@yahoo.fr \
--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).