On Wed, 24 Jul 2013 08:48:27 +0200 Michal Simek <mon...@monstr.eu> wrote:
> On 07/24/2013 07:55 AM, Rich Felker wrote: > > On Wed, Jul 24, 2013 at 07:34:07AM +0200, Michal Simek wrote: > >> Microblaze was assign to CLONE_BACKWARDS type where > >> parent tid was passed via 3rd argument. > >> Microblaze glibc is using 4th argument for it. > >> > >> Create new CLONE_BACKWARDS3 type where stack_size is passed > >> via 3rd argument, parent thread id pointer via 4th, > >> child thread id pointer via 5th and tls value as 6th > >> argument > > > > I believe this also affects us in musl. What is the motivation for > > making a configure option that results in there being two incompatible > > syscall ABIs for the same arch? > > This sounds like a really bad idea... > > This patch fixes bug which was introduced by Al's patch where he moved > clone implementation from microblaze folder to generic location. That's important information which was omitted from the changelog. Please identify the patch which casused this regression (SHA hash and title), thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
