Re: attribute handler oddness in MEP and STORMY16 ports

2014-12-02 Thread DJ Delorie
My memories of why I did MeP the way I did are... vague. I recall it had to do with getting the attributes to apply to C++ objects correctly, since C++ objects tend to be "complicated" and gcc didn't always pass me what I expected. > think they are suppose to. They build, but I cant test them.

Re: attribute handler oddness in MEP and STORMY16 ports

2014-11-28 Thread Andrew MacLeod
btw, a bit of followup... There were a few other ports that had checks similar to that in their handlers.. ie in rs6000.c:rs6000_handle_longcall_attribute() and i386:ix86_handle_cconv_attribute() if (TREE_CODE (*node) != FUNCTION_TYPE && TREE_CODE (*node) != FIELD_DECL && TREE_CO

attribute handler oddness in MEP and STORMY16 ports

2014-11-28 Thread Andrew MacLeod
While going through the attribute tables to sort out separation or trees and types, I'm seeing a couple of ports with similar handlers that look a little odd. the code sequence in the handler looks like: if (TREE_CODE (*node) != VAR_DECL && TREE_CODE (*node) != POINTER_TYPE && TREE