Dave Korn - RE: [PATCH] Re: ref_contains_indirect_ref always false? (original) (raw)
This is the mail archive of the gcc@gcc.gnu.orgmailing list for the GCC project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] |
- From: "Dave Korn"
- To: "'Daniel Berlin'"
- Cc:
- Date: Fri, 4 Nov 2005 16:37:04 -0000
- Subject: RE: [PATCH] Re: ref_contains_indirect_ref always false?
Daniel Berlin wrote:
[cc list trimmed because it's just one of those silly friday afternoon things]
On Fri, 2005-11-04 at 16:23 +0000, Dave Korn wrote:
Daniel Berlin wrote:
The use in tree-ssa-loop-niter.c is really trying to skip out on inferring loop bounds from pointer to structure accesses in the case of things like:
struct a { char foo[1]; };
struct a *b = malloc (sizeof (struct a) + 100); b->foo = "I like candy!"
Since we have to keep this working:)
We do?! Storing a pointer value to a char variable has never worked very well so far!
I was shorthanding it, you know what i meant :)
heh, yeh, I knew.
But I see so many lines like that in C programs written by people who think they're writing in C++ [*] ....
cheers,
DaveK[*] Or BASIC, even more likely!
Can't think of a witty .sigline today....
- References:
- RE: [PATCH] Re: ref_contains_indirect_ref always false?
* From: Daniel Berlin
- RE: [PATCH] Re: ref_contains_indirect_ref always false?
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |