I've been looking over the reviews as well as a few things I've encountered locally, and collected this list:
Unfortunately, I am simply not familiar enough with the gcc tree to implement patch 16, although there is a slight possibility that I may be able to do patch 19, and a stronger one that I could do patch 16. (Although I have been working on patch 19 and 16 for a few months now and with little success). I can definitely do patch 53, and am working on that. While patch 13, 16 and 19 are all sub-par solutions, they are solutions, and as such implementing better solutions is a lower priority than fixing the remaining issue, the -dumpbase caused linker error. I would very much appreciate help in that area specifically, as once that is solved we'll have a working compiler and library, and then I can focus on improving the library. (Patch 13) Re-add flag_evaluation_order, reorder_operands_p, and add reorder bool argument to tree_swap_operands_p: Replace with front-end specific function ala flag_strong_eval_order (Patch 16) gcc: Re-add TYPE_METHODS: Remove, replace instances of TYPE_METHODS with TYPE_FIELDS in the java frontend (Patch 19) Revert "Move void_list_node init to common code". (8ff2a92a0450243e52d3299a13b30f208bafa7e0): Remove, handle properly in Java frontend. Breakage caused by 1dedc12d186a110854537e1279b4e6c29f2df35a: Changes to -dumpbase cause undefined link errors, fix usage of -dumpbase in gcc/java/jvspec.cc (Patch 53) classpath: Use modern autotools mkdir -p handling: Find way to make MKDIR_P propagate to generated copy-vmresources.sh
