🚀 go-pugleaf

I don't read this newsgroup so I don't know if this is a well documented
problem.  I apologize if I am beating the same dead horse into a thin soup.

We are having the following problem with gcc and gas on our Sequent. We use
the -fshared-data flag on gcc to get external variables in compilation
units into the shared data-area. However, gas does not understand the
shared-data pseudo-opcode generated by gcc, which does seem a might
inconsistent. Our current fix is to use the Sequent assembler and then lose
some gdbx capabilities. Not great but livable.

However, the problem has now become acute with the recent distribution of
our light-weight process software which relies on gcc -fshared-data for
compilation on Sequents. Most sites have the standard GNU installation
which includes the use of gas. So our software does not compile. Clearly,
there are several work arounds but none that are simple and still preserve
the full power of gdbx. It would be most convenient if gcc and gas were in
step.

Thanks for listening to our problem. Love your software. Please reply
direct to me as I don't read this group.