> I asked about the idea of <machine/pubassym.h> on three separate
> occassions over the course of more than a month.  I received absolutely
> zero comments on this.  I described this once on developers, once on
> port-mips and once by providing the code for review for a week prior to
> committing it.  While this certainly does not mean that one forfeits
> the right to comment on changes, a a certain civility is appropriate when
> commenting at such a late date.

I'm very sorry for late about commenting.
Actually I had to pay more attentions about your proposal. Sorry.

> It would be helpful to point out why something breaks a standard to
> help create a solution.  I presume the POSIX/ANSI C issues  concern
> namespace pollution.  Is using a single underscore prefix sufficient?
> Double underscores?  Trailing underscores?

This is indeed one of the problem.

But the most important problem is BINARY COMPATIBILITY.
Kernel configuration should NOT affect the ABI.
So, the mechanism like the <machine/pbassym.h> is wrong.
It automatically breaks binary compatibility between the systems
with different kernel configurations.

If it is automatically generated, binary compatibility may be broken
without notificaiton. So, it should be maintained MANUALLY.
This is why _JBLEN is hardcoded in prior <mips/setjmp.h> and
other architecture's <machine/setjmp.h>.

So, please remove the mechanism which reflect kernel configuration
to userland. Please.
--
soda