[rl78]: Port to new pass C++ API (was Re: [buildbot] r201508: Build failures after pass C++ conversion)

2013-08-06 Thread David Malcolm
On Tue, 2013-08-06 at 13:18 +0200, Jan-Benedict Glaw wrote: On Tue, 2013-08-06 13:12:57 +0200, Jan-Benedict Glaw jbg...@lug-owl.de wrote: On Mon, 2013-08-05 20:16:05 -, dmalc...@gcc.gnu.org dmalc...@gcc.gnu.org wrote: New Revision: 201508 URL:

Re: [rl78]: Port to new pass C++ API (was Re: [buildbot] r201508: Build failures after pass C++ conversion)

2013-08-06 Thread DJ Delorie
Go for it. The static 212 is not required as long as the pass shows up in the right spot in the pass sequence.

Re: [rl78]: Port to new pass C++ API (was Re: [buildbot] r201508: Build failures after pass C++ conversion)

2013-08-06 Thread David Malcolm
On Tue, 2013-08-06 at 19:53 -0400, DJ Delorie wrote: Go for it. The static 212 is not required as long as the pass shows up in the right spot in the pass sequence. Thanks. I checked, and both with and without the hardcoded 212, the dumpfile for the pass for a foo.c is currently: