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] New: [4.7 Regression] libgo ftbfs on arm-linux-gnueabi (unknown case for SETCONTEXT_CLOBBERS_TLS) Date: Sun, 12 Feb 2012 17:03:00 -0000 [thread overview] Message-ID: <bug-52218-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52218 Bug #: 52218 Summary: [4.7 Regression] libgo ftbfs on arm-linux-gnueabi (unknown case for SETCONTEXT_CLOBBERS_TLS) Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: go AssignedTo: ian@airs.com ReportedBy: doko@gcc.gnu.org built with 20120205, fails with 20120210: ../../../src/libgo/runtime/proc.c:105:4: error: #error unknown case for SETCONTEXT_CLOBBERS_TLS ../../../src/libgo/runtime/proc.c: In function 'runtime_gogo': ../../../src/libgo/runtime/proc.c:299:2: error: implicit declaration of function 'fixcontext' [-Werror=implicit-function-declaration] ../../../src/libgo/runtime/proc.c: In function 'runtime_schedinit': ../../../src/libgo/runtime/proc.c:366:2: error: implicit declaration of function 'initcontext' [-Werror=implicit-function-declaration] cc1: all warnings being treated as errors make[6]: *** [proc.lo] Error 1
next reply other threads:[~2012-02-12 17:03 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-12 17:03 doko at gcc dot gnu.org [this message] 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 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@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: linkBe 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).