This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: How to debug ssa optimizer
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- To: dnovillo at redhat dot com
- Cc: gcc at gcc dot gnu dot org
- Date: Sat, 19 Jun 04 22:25:33 EDT
- Subject: Re: How to debug ssa optimizer
Hmm? They're both compatible, v_386 is pointing to the first element of
version_string.
Yes, but "&version_string" is a shorthand for
<ADDR_EXPR <VAR_DECL version_string>>
and that has a type of an ARRAY_TYPE. So what's happening later is
that we have a MODIFY_EXPR whose LHS is a char and whose RHS is an
ARRAY_TYPE.
I think I'm approaching where it's happening in GDB ...
Unfortunately, statements have no UIDs in GIMPLE. You can do indirect
things like setting a breakpoint at the basic block number and then step
until you reach the statement. Adding UIDs to GIMPLE statements would
be a fine addition for debugging.
Perhaps we can resurrect TREE_COMPLEXITY. ;-)