This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Ada bootstrap failure due to loop optimization and builtin_stack_alloc
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- To: rakdver at atrey dot karlin dot mff dot cuni dot cz
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 30 Jul 04 08:49:49 EDT
- Subject: Re: Ada bootstrap failure due to loop optimization and builtin_stack_alloc
because rewriting every use of the variable sized array via indirection
makes debugging impossible, basically.
It doesn't make it "impossible", it just means that there's a level of
indirection there that the programmer won't expect to see in the debugger.
If you use a REFERENCE_TYPE instead of a POINTER_TYPE, it's actually a
little cleaner.
Ada does this in cases where there's no choice (e.g., a global of
variable size) and you can indeed debug it, but see the indirection.
But yes, as noted further in the thread, this seems like a best solution
regardless.
I agree with that: it's not that common a case to justify adding a
large level of complication to GIMPLE to deal with it.