public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/52218] [4.7 Regression] libgo ftbfs on arm-linux-gnueabi (unknown case for SETCONTEXT_CLOBBERS_TLS)
Date: Tue, 21 Feb 2012 14:13:00 -0000	[thread overview]
Message-ID: <bug-52218-4-Tivuu062Mi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52218-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52218

Matthias Klose <doko at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW

--- Comment #4 from Matthias Klose <doko at gcc dot gnu.org> 2012-02-21 13:36:44 UTC ---
Peter Maydell commented:

Specifically the functions exist but return ENOSYS, which is why this:
  if (getcontext (&c) < 0)
    abort ();

will abort.

Trying to get these functions into eglibc for ARM is kind of on the Linaro
toolchain group's todo list, but (a) not at a hugely high priority and (b) it
will take a little while for them to percolate through eglibc and back into
distros anyway, so apps/configure scripts need to be prepared to handle the
returns-ENOSYS case anyway.


  parent reply	other threads:[~2012-02-21 13:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-12 17:03 [Bug go/52218] New: " doko at gcc dot gnu.org
2012-02-12 19:35 ` [Bug go/52218] " ian at airs dot com
2012-02-13 11:20 ` rguenth at gcc dot gnu.org
2012-02-14 18:21 ` ian at airs dot com
2012-02-16 16:27 ` doko at gcc dot gnu.org
2012-02-21 14:13 ` doko at gcc dot gnu.org [this message]
2012-02-21 18:42 ` ian at airs dot com
2012-03-06 20:25 ` [Bug go/52218] [4.7/4.8 " michael.hope at linaro dot org
2012-03-11 20:39 ` doko at gcc dot gnu.org

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=bug-52218-4-Tivuu062Mi@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).