This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c++/13776] [tree-ssa] Many C++ compile-time regression in 3.5-tree-ssa 040120


------- Additional Comments From rguenth at tat dot physik dot uni-tuebingen dot de  2004-03-13 16:53 -------
Subject: Re:  [tree-ssa] Many C++ compile-time regression in
 3.5-tree-ssa 040120

dberlin at dberlin dot org wrote:
> ------- Additional Comments From dberlin at dberlin dot org  2004-03-13 16:00 -------
> Subject: Re:  [tree-ssa] Many C++ compile-time regression in 3.5-tree-ssa 040120
> 
> 
>>and a lot more of int d farther away? Also, how are bb's marked? I see 
>><bb 0>: but no more, and some gotos reference <bb 18> and <bb 16> 
>>(with a label, too)?
>>
>>Can I get summaries somehow here?  Or just dump one interesting 
>>function rather than all of the program?
>>
>>Also, how do I dump some stuff about the PRE pass?  Specifying 
>>-fdump-tree-pre just dumps the trees after PRE with no information 
>>about the PRE pass itself.
> 
> 
> -fdump-tree-pre-stats-details. But i already know what it is going to 
> show in this case, based on the profile.
> I just need other properties of the functions, which i'm attempting to 
> get.

I also see we're running PRE before DCE - the functions probably contain 
  a lot of dead code - would it be sensible and profitable to move the 
first DCE pass before PRE?  Can this be specified on the command line or 
where would I need to change the source to do this?

Richard.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13776


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]