[Bug c++/67183] Darwin stub vs. non_lazy pointer ordering incompatible with clang assembler.

2015-08-12 Thread jay.krell at cornell dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67183 --- Comment #2 from Jay jay.krell at cornell dot edu --- er, three traversals. Also, ideally, nothing is ever output in hash order. At least not to assembly source and objects. It might be unavoidable for final executables. i.e. adding one

[Bug c++/67183] Darwin stub vs. non_lazy pointer ordering incompatible with clang assembler.

2015-08-12 Thread jay.krell at cornell dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67183 --- Comment #3 from Jay jay.krell at cornell dot edu --- https://github.com/modula3/cm3/commit/14d5e667e19abaab679b52bc8fd35a4e38073330 is a simple patch against 4.7 that establishes a partial ordering, separating the indirect functions from the

[Bug c++/67183] Darwin stub vs. non_lazy pointer ordering incompatible with clang assembler.

2015-08-12 Thread jay.krell at cornell dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67183 --- Comment #1 from Jay jay.krell at cornell dot edu --- It turns out, this looks easy to fix on the gcc side. See machopic_finish. Have it run two traversla instead of one. The first editing stubs, the second non-lazy pointers.