mips and proprietary instructions

Mike Frysinger vapier at gentoo.org
Sun Mar 25 20:52:56 UTC 2007


On Sunday 25 March 2007, JB wrote:
> The kernel is not the problem.  The processor will execute them if and
> when encountered.  The compiler already does not emit them.  It is the
> memcpy.S code distributed in any version of uClibc > 0.9.26 that has
> them already in assembly form.  I would be rewriting the mips assembly
> and the last mips assembly I worked on was many many years ago.  I would
> have thought the open source community would have opposed the
> proprietary instructions and worked to avoid them in the first place...
> Has no one dealt with this?  I searched on google for quite a while and
> was unable to find any kind of existing solution out there.

you say "proprietary instructions" yet you dont actually provide any real 
examples of what you're talking about

just because your outdated assembler does not recognize the opcode does not 
mean the code in question is proprietary
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
Url : http://lists.busybox.net/pipermail/uclibc/attachments/20070325/7a0c9a37/attachment-0002.pgp 


More information about the uClibc mailing list