From: Zack Weinberg <zack@codesourcery.com>
To: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
Cc: pinskia@physics.uc.edu, gcc-patches@gcc.gnu.org
Subject: Re: [patch] for PR 18040
Date: Sun, 17 Oct 2004 23:45:00 -0000 [thread overview]
Message-ID: <87is98syjj.fsf@codesourcery.com> (raw)
In-Reply-To: <10410172240.AA01890@vlsi1.ultra.nyu.edu> (Richard Kenner's message of "Sun, 17 Oct 04 18:40:41 EDT")
kenner@vlsi1.ultra.nyu.edu (Richard Kenner) writes:
> The way to fix this would be take the address and cast that pointer
> to the pointer of the new type.
>
> That only works when it's addressable. In the case of a variable it is,
> but not when it's an intermediate field.
I wish you would have given me an example that wasn't susceptible to
fixing by taking the address of the aggregate, then.
Hmm. Is it possible to construct an example which BOTH requires
taking the address of an intermediate field, and wouldn't be cured by
making all *_REF expressions implicitly convert to their type?
zw
next prev parent reply other threads:[~2004-10-17 23:41 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 23:06 Richard Kenner
2004-10-17 23:45 ` Zack Weinberg [this message]
2004-10-18 0:23 ` Zack Weinberg
-- strict thread matches above, loose matches on Subject: below --
2004-10-20 13:27 Richard Kenner
2004-10-20 0:25 Richard Kenner
2004-10-19 23:26 Richard Kenner
2004-10-19 23:22 Richard Kenner
2004-10-19 23:03 Richard Kenner
2004-10-19 23:13 ` Jason Merrill
2004-10-19 22:48 Richard Kenner
2004-10-19 23:01 ` Jason Merrill
2004-10-19 23:07 ` Zack Weinberg
2004-10-18 17:48 Richard Kenner
2004-10-18 15:42 Richard Kenner
2004-10-18 14:52 Richard Kenner
2004-10-18 15:20 ` Daniel Berlin
2004-10-18 14:38 Richard Kenner
2004-10-18 14:24 Richard Kenner
2004-10-19 22:50 ` Zack Weinberg
2004-10-18 14:22 Richard Kenner
2004-10-19 22:47 ` Zack Weinberg
2004-10-18 3:12 Richard Kenner
2004-10-18 4:02 ` Zack Weinberg
2004-10-18 4:26 ` Daniel Berlin
2004-10-18 2:46 Richard Kenner
2004-10-18 2:38 Richard Kenner
2004-10-18 3:14 ` Zack Weinberg
2004-10-18 2:35 Richard Kenner
2004-10-18 2:51 ` Zack Weinberg
2004-10-17 22:30 Richard Kenner
2004-10-17 22:36 ` Andrew Pinski
2004-10-17 23:41 ` Zack Weinberg
2004-10-18 13:13 ` Florian Weimer
2004-10-18 17:24 ` Jason Merrill
2004-10-18 17:37 ` Florian Weimer
2004-10-18 18:02 ` Jason Merrill
2004-10-19 22:40 ` Zack Weinberg
2004-10-17 21:24 Richard Kenner
2004-10-17 21:43 ` Zack Weinberg
2004-10-17 21:18 Richard Kenner
2004-10-17 21:26 ` Zack Weinberg
2004-10-17 21:04 Richard Kenner
2004-10-17 21:10 ` Zack Weinberg
2004-10-19 21:36 ` Richard Henderson
2004-10-19 22:19 ` Daniel Berlin
2004-10-20 7:03 ` Jason Merrill
2004-10-19 22:51 ` Zack Weinberg
2004-10-20 0:02 ` Richard Henderson
2004-10-17 20:25 Richard Kenner
2004-10-17 20:47 ` Daniel Berlin
2004-10-17 20:17 Richard Kenner
2004-10-17 20:25 ` Daniel Berlin
2004-10-17 19:46 Richard Kenner
2004-10-17 19:46 ` Daniel Berlin
2004-10-17 19:48 ` Zdenek Dvorak
2004-10-17 20:01 ` Daniel Berlin
2004-10-17 19:28 Zdenek Dvorak
2004-10-19 21:36 ` Richard Henderson
2004-10-19 22:03 ` Zdenek Dvorak
2004-10-19 22:04 ` Andrew Pinski
2004-10-19 22:06 ` Zdenek Dvorak
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=87is98syjj.fsf@codesourcery.com \
--to=zack@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
--cc=pinskia@physics.uc.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).