7 msgRFC: Creating a live, all-encompassing architec...
53 msgGCC 4.3 release schedule
4 msgAutovectorized HIRLAM - latest results.
5 msgHow widely used are <ext/hash_set> and &l...
1 msgGCC 4.3.0 Status Report (2007-10-25)
3 msgproblem with iv folding
2 msgAny Ada changes for GCC 4.3?
10 msgalias and pointers analysis
3 msgDecimal question and sqrt in math.h
54 msg-fno-tree-cselim not working?
5 msglicense for libgcc source files
1 msggcc-4.2-20071024 is now available
16 msgcannot pass objects of non-POD type

A question about df
\ Revital1 Eres (24 Oct 2007)
. \ Seongbae Park (¹Ú¼º¹è, ÚÓà÷ÛÆ) (24 Oct 2007)
. . \ Revital1 Eres (24 Oct 2007)
. . . \ Seongbae Park (¹Ú¼º¹è, ÚÓà÷ÛÆ) (24 Oct 2007)

2 msgRTL/VCG inconsistency (the check_match.7758 case)
3 msghelp in deciphering a call RTL instruction
3 msgregister variables: list?
1 msgIs peephole2 expansion recursive?
1 msg[RFC PING] INSN attribute to enable/disable alt...
2 msgProblem when build glibc on IA64
Subject:A question about df
Group:Gcc
From:Revital1 Eres
Date:24 Oct 2007



Hello,

While testing a patch for the SMS I got an ICE which seems
to be related to the fact we build def-use chains only
and not use-def chains. (removed in the following patch -
http://gcc.gnu.org/ml/gcc-patches/2006-12/msg01682.html)

The problem arises when we delete an insn from the df that contains a
use but do not update the def-use chain of it's def as we do not have
the use-def chain to reach it's def, This later causes a problem when
we try to dump the def-use chain of it's def.

So, it seems that when asking for only def-use problem and later dump
the function we should ask for use-def problem as well to avoid cases
like the above.

Thanks,
Revital



© 2004-2008 readlist.com