shouldn't every middle-end pass be uniquely named?

2008-07-31 Thread Basile STARYNKEVITCH
Hello All, Some middle-end passes (those declared in tree-passes.h) are still unnamed. I tend to believe that it would be helpful (mostly for gcc debugging purposes) that every struct opt_pass (without exception) should be uniquely named (and that this should be enforced, eg. in

Re: shouldn't every middle-end pass be uniquely named?

2008-07-31 Thread Andrew Thomas Pinski
Sent from my iPhone On Jul 31, 2008, at 1:11, Basile STARYNKEVITCH [EMAIL PROTECTED] wrote: Hello All, Some middle-end passes (those declared in tree-passes.h) are still unnamed. I tend to believe that it would be helpful (mostly for gcc debugging purposes) that every struct

Re: shouldn't every middle-end pass be uniquely named?

2008-07-31 Thread Basile STARYNKEVITCH
Andrew Thomas Pinski wrote: Sent from my iPhone Except as a habit (which I think is a bad one) is there any reason to have anonymous passes (those with a null pass-name), or (I don't know if such beast exists) homonym passes (two different passes with equal pass-name)? Yes. To prevent a

Re: shouldn't every middle-end pass be uniquely named?

2008-07-31 Thread Basile STARYNKEVITCH
Basile STARYNKEVITCH wrote: Andrew Thomas Pinski wrote: Except as a habit (which I think is a bad one) is there any reason to have anonymous passes (those with a null pass-name), or (I don't know if such beast exists) homonym passes (two different passes with equal pass-name)? Yes. To