This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Add CONSTRUCTOR case to loc_descriptor_from_tree in dwarf2out.c
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- To: rth at redhat dot com
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Thu, 31 Jul 03 21:21:28 EDT
- Subject: Re: Add CONSTRUCTOR case to loc_descriptor_from_tree in dwarf2out.c
> Sure, but is it worth it for just that case?
Wrong is wrong, isn't it?
But is this "wrong"? Can you actually ever have a case where a CONSTRUCTOR
is used in a bound/size/location description and not in code? If it were
easy to check for, fine, but I don't see the justification for adding a
whole new function.
How about just modifying it to take a DEFER value of -1 that says to return
0 if the constant hasn't already been output? That still might be a case
that can't ever occur, but at least the "damage" is smaller.