I have it seemingly working now, much better, thanks for the nudges -- that
indeed high id is invalid, and to look again at my GTY use.
I don't know if it made the difference but I changed some whitespace to match
others, and
typedef struct foo_t { ... } foo_t;
to
typedef struct foo { ... } foo_
;VEC" or even use a fixed size and see what
happens..
Thanks,
- Jay
> From: jay.kr...@cornell.edu
> To: i...@google.com
> CC: gcc@gcc.gnu.org
> Subject: RE: internal compiler error: in referenced_var_lookup, at tree-dfa.c
> Date: Sat,
.c:1950
and some other problems..I really need to fix those...
- Jay
> From: jay.kr...@cornell.edu
> To: i...@google.com
> CC: gcc@gcc.gnu.org
> Subject: RE: internal compiler error: in referenced_var_lookup, at tree-dfa.c
> Date: Fri, 10 Se
[licensing dealt with separately]
> > Variable: D.1093058884, UID D.1093058884, int_32gimple_default_def
> > 0x412130a8 1093058884
> This is clearly wrong, though I have no idea what caused it.
> > Is it valid for uids to be so high?
> No.
Thanks, that helps.
> From your description, you've
ks a chance to not "like" me and not
help me.
I'll address the technical part separately.
Thanks,
- Jay
> Date: Fri, 10 Sep 2010 11:17:59 -0400
> From: de...@adacore.com
> To: i...@google.com
> CC: jay.kr...@cornell.edu; gcc
On 9/10/2010 11:08 AM, Ian Lance Taylor wrote:
Jay K writes:
That uses process boundaries to avoid GPL crossing into BSDish licensed code.
So maybe you don't want to help me. Understood.
Note that different people have different opinions as to whether a
process boundary means that your code
Jay K writes:
> That uses process boundaries to avoid GPL crossing into BSDish licensed code.
> So maybe you don't want to help me. Understood.
Note that different people have different opinions as to whether a
process boundary means that your code is not a derived work. Not that
we should get
ccesses by offseting pointers and
casting.
We do our own layout earlier. Not great, but that's how it is.
Currently we use gcc 4.5.1.
When I enable inlining on some architectures, e.g. Macosx/x86, much code yields:
../FPrint.m3: In function 'FPrint__xCombine':
../FPrint.m3:25:0: in
