From: Michael Haubenwallner <michael.haubenwallner@salomon.at>
To: gcc-help@gcc.gnu.org
Subject: does this code break the strict-aliasing rules ?
Date: Tue, 06 Feb 2007 15:58:00 -0000 [thread overview]
Message-ID: <1170777494.30181.38.camel@sapc154> (raw)
Hi,
encountering strange results, I'm unsure whether this code is affected
by strict-aliasing rules:
static void *CreateRes(PrexecTresource eRes, void *pvVal)
{
switch(eRes) {
case PrexecNprintCommand:
case PrexecNoptHost:
case PrexecNoptHostString:
case PrexecNoptDest:
case PrexecNoptDestString:
case PrexecNoptFileString:
if (pvVal != NULL) {
pvVal = (void*)strdup((char*)pvVal);
}
break;
default:
break;
}
return pvVal;
}
Specifically the casts around the 'strdup'...
Thanks,
/haubi/
next reply other threads:[~2007-02-06 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 15:58 Michael Haubenwallner [this message]
2007-02-06 16:02 ` Andrew Haley
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=1170777494.30181.38.camel@sapc154 \
--to=michael.haubenwallner@salomon.at \
--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).