From: mark@codesourcery.com
To: nik@tiuk.ti.com
Cc: tim@franck.Princeton.EDU, egcs@egcs.cygnus.com, george@moberg.com
Subject: Re: Clarification anyone? -- was Re: Linux and aliasing?
Date: Tue, 08 Jun 1999 10:41:00 -0000 [thread overview]
Message-ID: <19990608104553V.mitchell@codesourcery.com> (raw)
In-Reply-To: <199906081732.SAA13273@tiuk.ti.com>
>>>>> "Nick" == Nick Ing-Simmons <nik@tiuk.ti.com> writes:
Nick> I assume unions are exempt from this?
Somewhat. Please see the manual section I just posted for more
information.
Nick> What is proposed is that any mem-assign can be considered to
Nick> "clobber" any value of the same type, and an assign via a
Nick> char * to clobber anything ?
Right.
Nick> And thus problem is that if I do this:
Nick> int a; *((short *) &a) = 123;
Nick> Then 'a' is not considered clobbered?
Right.
Nick> Even in the same function?
Right.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
WARNING: multiple messages have this Message-ID
From: mark@codesourcery.com
To: nik@tiuk.ti.com
Cc: tim@franck.Princeton.EDU, egcs@egcs.cygnus.com, george@moberg.com
Subject: Re: Clarification anyone? -- was Re: Linux and aliasing?
Date: Wed, 30 Jun 1999 15:43:00 -0000 [thread overview]
Message-ID: <19990608104553V.mitchell@codesourcery.com> (raw)
Message-ID: <19990630154300.dhNBTWD8iDlDT-53w8BZYSV1sYE1rXm8m4c1CUKiXqs@z> (raw)
In-Reply-To: <199906081732.SAA13273@tiuk.ti.com>
>>>>> "Nick" == Nick Ing-Simmons <nik@tiuk.ti.com> writes:
Nick> I assume unions are exempt from this?
Somewhat. Please see the manual section I just posted for more
information.
Nick> What is proposed is that any mem-assign can be considered to
Nick> "clobber" any value of the same type, and an assign via a
Nick> char * to clobber anything ?
Right.
Nick> And thus problem is that if I do this:
Nick> int a; *((short *) &a) = 123;
Nick> Then 'a' is not considered clobbered?
Right.
Nick> Even in the same function?
Right.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~1999-06-08 10:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-08 6:42 george
1999-06-08 7:33 ` Tim Hollebeek
1999-06-08 8:24 ` Jamie Lokier
1999-06-30 15:43 ` Jamie Lokier
1999-06-08 10:33 ` Nick Ing-Simmons
1999-06-08 10:41 ` mark [this message]
1999-06-08 15:47 ` Martin v. Loewis
1999-06-30 15:43 ` Martin v. Loewis
1999-06-30 15:43 ` mark
1999-06-30 15:43 ` Nick Ing-Simmons
1999-06-30 15:43 ` Tim Hollebeek
1999-06-08 10:20 ` mark
1999-06-08 13:50 ` Ross Smith
1999-06-09 0:40 ` Martin v. Loewis
1999-06-30 15:43 ` Martin v. Loewis
1999-06-30 15:43 ` Ross Smith
1999-06-30 15:43 ` mark
1999-06-08 15:06 ` Martin v. Loewis
1999-06-11 10:01 ` James Antill
1999-06-30 15:43 ` James Antill
1999-06-30 15:43 ` Martin v. Loewis
1999-06-30 15:43 ` george
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=19990608104553V.mitchell@codesourcery.com \
--to=mark@codesourcery.com \
--cc=egcs@egcs.cygnus.com \
--cc=george@moberg.com \
--cc=nik@tiuk.ti.com \
--cc=tim@franck.Princeton.EDU \
/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).