[M3devel] reducing our diff to gcc?
Jay K
jay.krell at cornell.edu
Sun Jun 10 10:34:36 CEST 2012
reducing our diff to gcc?
Ignore my hacking: extern C, removal of optimizer, removal of gmp/mpfr/mpc..
but wait: do people like removal of gmp/mpfr/mpc? I do. I'm torn.
But to my point:
gimplify.c: I think we can achieve the diff via langhook.gimplify_expr.
tree.def: I think frontends can add their own codes in separate files, so the diff can be removed.
but, tree-nested.c, I doubt this can be avoided..so I'm left probably
just not bothering with the others.
Thoughts?
There is also at least one bug fix...that I could avoid needing.
There is a bug optimizing our form of div/mod.
We could avoid that by going back to function calls, but..again, I'm torn.
If you configure -enable-checking, at least currently, there are asserts that have to be removed.
I think I'll just go ahead and patch 4.7 "completely", w/o overdoing it.
- Jay
More information about the M3devel
mailing list