public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63534] [5 Regression] Bootstrap failure on x86_64/i686-linux
Date: Tue, 14 Oct 2014 17:18:00 -0000 [thread overview]
Message-ID: <bug-63534-4-6kgr0jCYjc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63534-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63534
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
--- Comment #7 from Jeffrey A. Law <law at redhat dot com> ---
I'd strongly recommend against option #1 to deal with PIC vs profiling. We
don't want to have two distinct implementations for PIC support in 32 bit mode.
I've got no strong opinions on Jakub's proposal, or emitting a second set_got
after the profiling bits.
next prev parent reply other threads:[~2014-10-14 17:18 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 12:31 [Bug target/63534] New: " jakub at gcc dot gnu.org
2014-10-14 12:46 ` [Bug target/63534] " rguenth at gcc dot gnu.org
2014-10-14 13:20 ` evstupac at gmail dot com
2014-10-14 13:50 ` jakub at gcc dot gnu.org
2014-10-14 14:20 ` evstupac at gmail dot com
2014-10-14 14:56 ` jakub at gcc dot gnu.org
2014-10-14 16:27 ` iverbin at gcc dot gnu.org
2014-10-14 17:18 ` law at redhat dot com [this message]
2014-10-15 7:31 ` jakub at gcc dot gnu.org
2014-10-15 8:22 ` dominiq at lps dot ens.fr
2014-10-15 16:07 ` evstupac at gmail dot com
2014-10-15 16:18 ` vmakarov at gcc dot gnu.org
2014-10-15 16:30 ` evstupac at gmail dot com
2014-10-15 18:13 ` dominiq at lps dot ens.fr
2014-10-16 11:32 ` evstupac at gmail dot com
2014-10-16 12:33 ` dominiq at lps dot ens.fr
2014-10-16 14:40 ` iains at gcc dot gnu.org
2014-10-16 15:33 ` dominiq at lps dot ens.fr
2014-10-16 19:07 ` iains at gcc dot gnu.org
2014-10-16 20:59 ` izamyatin at gmail dot com
2014-10-16 23:54 ` iains at gcc dot gnu.org
2014-10-17 12:08 ` evstupac at gmail dot com
2014-10-17 12:55 ` iains at gcc dot gnu.org
2014-10-17 12:57 ` iains at gcc dot gnu.org
2014-10-17 13:48 ` evstupac at gmail dot com
2014-10-17 15:06 ` dominiq at lps dot ens.fr
2014-10-17 16:56 ` law at redhat dot com
2014-10-17 17:05 ` iains at gcc dot gnu.org
2014-10-20 10:17 ` evstupac at gmail dot com
2014-10-20 10:18 ` evstupac at gmail dot com
2014-10-21 16:21 ` evstupac at gmail dot com
2014-10-22 20:36 ` iains at gcc dot gnu.org
2014-10-22 20:51 ` evstupac at gmail dot com
2014-10-23 16:54 ` iverbin at gcc dot gnu.org
2014-10-24 14:17 ` ro at gcc dot gnu.org
2014-10-24 14:35 ` evstupac at gmail dot com
2014-10-24 15:26 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-10-24 15:46 ` evstupac at gmail dot com
2014-10-24 16:37 ` law at redhat dot com
2014-10-24 17:29 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-10-27 10:04 ` dominiq at lps dot ens.fr
2014-10-28 14:32 ` izamyatin at gmail dot com
2014-10-29 22:09 ` dominiq at lps dot ens.fr
2014-10-30 4:44 ` law at redhat dot com
2014-10-31 13:37 ` ienkovich at gcc dot gnu.org
2014-11-06 22:16 ` howarth at bromo dot med.uc.edu
2014-11-06 22:41 ` evstupac at gmail dot com
2014-11-07 0:00 ` evstupac at gmail dot com
2014-11-07 1:18 ` howarth at bromo dot med.uc.edu
2014-11-07 9:52 ` marxin at gcc dot gnu.org
2014-11-07 11:46 ` howarth at bromo dot med.uc.edu
2014-11-07 13:52 ` howarth at bromo dot med.uc.edu
2014-11-07 14:15 ` howarth at bromo dot med.uc.edu
2014-11-07 14:49 ` dominiq at lps dot ens.fr
2014-11-07 15:20 ` howarth at bromo dot med.uc.edu
2014-11-07 20:43 ` kyukhin at gcc dot gnu.org
2014-11-11 10:13 ` fxcoudert at gcc dot gnu.org
2014-11-11 12:15 ` izamyatin at gmail dot com
2014-11-11 12:21 ` fxcoudert at gcc dot gnu.org
2014-11-11 12:39 ` dominiq at lps dot ens.fr
2014-11-20 11:22 ` fxcoudert at gcc dot gnu.org
2014-11-20 11:22 ` fxcoudert at gcc dot gnu.org
2014-11-25 21:08 ` hjl 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-63534-4-6kgr0jCYjc@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).