Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] jack2: Try better fix for NGREG problem
Date: Mon, 21 Nov 2016 15:54:34 +0100	[thread overview]
Message-ID: <20161121155434.728d1acb@free-electrons.com> (raw)
In-Reply-To: <1479739795-31046-1-git-send-email-abrodkin@synopsys.com>

Hello,

On Mon, 21 Nov 2016 17:49:55 +0300, Alexey Brodkin wrote:
> After quite some time trying this and that we seem to have no
> better solution than proposed by Thomas back in the day [1].
> 
> The solution in question is to check [during jack2 configuration]
> if NGREG is exposed via ucontext.h and then use its value in
> source code later on. This replaces long and still growing list
> of architectures for which we explicitly escape usage of NGREG.
> 
> Just for reference [2] is my attempt to fix in in the other
> supposedly better way but with no luck because of the mess in
> kernel's UAPI headers.
> 
> [1] http://lists.busybox.net/pipermail/buildroot/2016-May/161785.html
> [2] http://lists.busybox.net/pipermail/buildroot/2016-June/162461.html
> 
> Still not sure if that works for every other architectures, so testing
> and Acks from all interested parties are much appreciated.

Unfortunately, I experimented with something like this some time ago,
and IIRC, it didn't work all architectures, because NGREG is not always
defined in <ucontext.h>, but can be defined in other header files (if I
recall). In the end, I think I ended up with something like the below,
but I don't remember if I tested it in all cases:

(As you can see, it dates back from May 2016...)

  reply	other threads:[~2016-11-21 14:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-21 14:49 [Buildroot] [PATCH] jack2: Try better fix for NGREG problem Alexey Brodkin
2016-11-21 14:54 ` Thomas Petazzoni [this message]
2016-11-21 14:58   ` Alexey Brodkin
2016-12-17 16:22 ` Thomas Petazzoni
2016-12-19 15:57   ` Alexey Brodkin
2016-12-19 16:23     ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161121155434.728d1acb@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox