delorie.com/archives/browse.cgi | search |
X-Sybari-Space: | 00000000 00000000 00000000 00000000 |
From: | Martin Stromberg <Martin DOT Stromberg AT epl DOT ericsson DOT se> |
Message-Id: | <200304221509.RAA06409@lws256.lu.erisoft.se> |
Subject: | Re: Yet another try on nan in strto{f,d,ld} |
To: | djgpp-workers AT delorie DOT com |
Date: | Tue, 22 Apr 2003 17:09:07 +0200 (MET DST) |
In-Reply-To: | <3EA53652.200F23BD@phekda.freeserve.co.uk> from "Richard Dawe" at Apr 22, 2003 01:32:18 PM |
X-Mailer: | ELM [version 2.5 PL3] |
MIME-Version: | 1.0 |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
Richard said: > > I mean the plain typecasts, like this: > > > > + double_t n = *(double_t *)(&tmp_d); > > > > or this: > > > > + return *(double *)(&n); > [snip] > > As I understand it, restrict'ed variables are strictly aliased. Uuhhh... "strictly aliased"? Anyway, are you saying that tmp_d, n or *(double *)(&n) is strictly aliased, restrict qualified or in anyway will become so when we add restrict to the function's parameters? Why? Howcome? (Note that tmp_d and n are local variables.) Right, MartinS
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |