https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119377
--- Comment #13 from Robert Dubner <rdubner at gcc dot gnu.org> --- Thanks. Sadly, that didn't tell me anything useful. The front-end code that's failing is slated to be completely eliminated when Jim gets a chance to work on it, probably in the next couple of weeks. The COBOLworx suite has numerous DECLARATIVE testcases. But declarative_1 is the only DejaGnu test with DECLARATIVE, so if it's the only one failing for you, I think the most expedient solution is to simply delete the thing for now. After Jim rewrites the offending code, we'll introduce it again. But if other testcases are failing, that becomes less attractive. Let me know. Given how it's failing, it'll probably fail again. I say that because of where the problem is manifesting, which is pretty high up in the parser. So, if you can give me some guidance on setting up a Darwin development environment, that'll be useful, so we're not trying to debug by remote control. I mean, I don't have a clue even as to what compiler you are using to compile GCC-16!
