public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/9762: Address of 'char' is incorrect.
Date: Thu, 20 Feb 2003 14:36:00 -0000	[thread overview]
Message-ID: <20030220143601.1434.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

The following reply was made to PR c/9762; it has been noted by GNATS.

From: Andreas Schwab <schwab@suse.de>
To: stephen.kennedy@havok.com
Cc: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org
Subject: Re: c/9762: Address of 'char' is incorrect.
Date: Thu, 20 Feb 2003 15:26:33 +0100

 stephen.kennedy@havok.com writes:
 
 |> #define TA char
 |> #define TB int
 |> #define TC int
 |> 
 |> void foobar(TA a, TB b, TC c);
 |> 
 |> int main()
 |> {
 |> 	foobar(1,2,3);
 |> 	return 0;
 |> }
 |> 
 |> void foobar(TA a, TB b, TC c)
 |> {
 |> 	printf("a == %i  claims %x\n", a, &a);
 |> 	printf("a == %i  really %x\n", (&b)[-1], (&b)-1);
 
 There is nothing in the C standard that requires that (char*)(&b-1) == &a.
 They are distinct objects, thus not comparable, and &b-1 by itself is
 already invalid.
 
 Andreas.
 
 -- 
 Andreas Schwab, SuSE Labs, schwab@suse.de
 SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
 Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
 "And now for something completely different."


             reply	other threads:[~2003-02-20 14:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 14:36 Andreas Schwab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-20 20:33 neil
2003-02-20 19:06 Daniel Jacobowitz
2003-02-20 18:36 Stephen Kennedy
2003-02-20  8:06 ebotcazou
2003-02-19 21:26 Neil Booth
2003-02-19 19:56 stephen.kennedy

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=20030220143601.1434.qmail@sources.redhat.com \
    --to=schwab@suse.de \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).