public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/55201] [4.8 regression] libgo.so: undefined reference to `__atomic_compare_exchange_8'
Date: Tue, 18 Dec 2012 14:29:00 -0000 [thread overview]
Message-ID: <bug-55201-4-00x09x2QKP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55201-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55201
--- Comment #2 from ian at gcc dot gnu.org <ian at gcc dot gnu.org> 2012-12-18 14:28:31 UTC ---
Author: ian
Date: Tue Dec 18 14:28:24 2012
New Revision: 194581
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=194581
Log:
libgo: Link against libatomic.
./:
PR go/55201
* Makefile.def (all-target-libgo): Depend on all-target-libatomic.
* Makefile.in: Regenerate.
gcc/go:
PR go/55201
* gospec.c (LIBATOMIC): Define.
(LIBATOMIC_PROFILE): Define.
(lang_specific_driver): Add LIBATOMIC[_PROFILE] option.
gcc/testsuite:
* lib/go.exp (go_link_flags): Add libatomic location to flags and
ld_library_path.
Modified:
trunk/ChangeLog
trunk/Makefile.def
trunk/Makefile.in
trunk/gcc/go/ChangeLog
trunk/gcc/go/gospec.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/lib/go.exp
trunk/libgo/Makefile.am
trunk/libgo/Makefile.in
next prev parent reply other threads:[~2012-12-18 14:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-04 7:54 [Bug go/55201] New: " schwab@linux-m68k.org
2012-11-04 12:46 ` [Bug go/55201] " schwab@linux-m68k.org
2012-11-05 16:28 ` jakub at gcc dot gnu.org
2012-12-07 9:30 ` rguenth at gcc dot gnu.org
2012-12-18 14:29 ` ian at gcc dot gnu.org [this message]
2012-12-18 14:45 ` schwab@linux-m68k.org
2012-12-18 22:04 ` ian at gcc dot gnu.org
2012-12-18 22:08 ` ian 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-55201-4-00x09x2QKP@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).