From: Jakub Jelinek <jakub@redhat.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
Andi Kleen <andi@firstfloor.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 1/2] Remove -fshort-double
Date: Mon, 29 Sep 2014 15:22:00 -0000 [thread overview]
Message-ID: <20140929152136.GF17454@tucnak.redhat.com> (raw)
In-Reply-To: <20140929152003.GA1629@tassilo.jf.intel.com>
On Mon, Sep 29, 2014 at 08:20:03AM -0700, Andi Kleen wrote:
> > As we saw LTO fixes for -fshort-double it's clear that this flag _is_ used
> > for some embedded archs.
>
> Did we? It has been ICEing since 4.5, which is before LTO.
Depends on which target. Aren't the ICEs i?86/x86_64 backend ICEs?
Jakub
next prev parent reply other threads:[~2014-09-29 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-27 13:55 Andi Kleen
2014-09-27 13:55 ` [PATCH 2/2] Make -Q --help print param defaults and min/max values Andi Kleen
2014-09-29 11:15 ` Richard Biener
2014-09-29 11:17 ` [PATCH 1/2] Remove -fshort-double Richard Biener
2014-09-29 15:20 ` Andi Kleen
2014-09-29 15:22 ` Jakub Jelinek [this message]
2014-09-29 15:31 ` Richard Biener
2014-09-29 15:48 ` Andi Kleen
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=20140929152136.GF17454@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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).