--- wikisrc/users/maya/vax-gcc.mdwn	2019/08/29 21:57:38	1.7
+++ wikisrc/users/maya/vax-gcc.mdwn	2019/09/15 12:56:38	1.12
@@ -1,6 +1,8 @@
 # Various GCC/vax issues and invesigation #
 
-## libgomp crash with -O2 ##
+[WIP tree](gcc-mirror/)
+
+## libgomp crash with -O2 [#58901](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58901) ##
 Repro:
 
     #!/bin/sh
@@ -22,6 +24,24 @@ NetBSD avoids it with a [local diff](htt
 It looks like a real bug in vax_legitimate_address_p not handling some addressing modes.  
 The code to handle offset(reg)[index] might be off: it doesn't like if neither xfoo0, xfoo1 are constant.
 
+
+## change_address_1, at emit-rtl.c:2286 [#85152](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85152) ##
+
+Repro:
+
+    #!/bin/sh
+
+    cat << EOF > oacc.i
+    void fn2();
+    unsigned a;
+    int fn1() {
+      int b = a >> 16;
+      if (b)
+        fn2();
+    }
+    EOF
+    vax--netbsdelf-gcc -O2 -c oacc.i
+
 ## unrecognizable insn with any optimization ##
 
 Repro:
@@ -64,4 +84,26 @@ This errors out with:
     during RTL pass: vregs
     /home/fly/oacc/decl.ii:17:1: internal compiler error: in extract_insn, at recog.c:2310
     
-Providing a trivial scheduling will avoid subregs of mem.
+
+This is in VAX-specific code. We need to figure out what instruction pattern this is, that we're missing.
+
+<!--Providing a trivial scheduling will avoid subregs of mem.  
+However, this doesn't work for us. Our crash and mem subregs happen at a too early pass, most likely.-->
+
+## DWARF ##
+
+    flag_dwarf2_cfi_asm = 0;
+
+is kind of a big deal. We should probably get rid of it, but [binutils hates that.](https://github.com/NetBSD/src/commit/1df57dce3744cf4743358b098728a0658b80b8fb)
+
+    ld: warning: dynamic relocation to `?' in readonly section `.eh_frame'
+    ld: warning: dynamic relocation to `?' in readonly section `.eh_frame'
+    ld: warning: creating a DT_TEXTREL in a shared object
+    ld: .eh_frame_hdr refers to overlapping FDEs
+    ld: final link failed: bad value
+
+[riscv seemed to share the issue](https://github.com/riscv/riscv-binutils-gdb/issues/76) and had fixed it.
+
+## review comments ##
+
+Jeff Law [provided some feedback](https://gcc.gnu.org/ml/gcc/2019-04/msg00281.html). More of it should be addressed.