public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gcc-patches@gcc.gnu.org
Subject: [ping] Re: RFA: Improve 128-bit long double configure test
Date: Thu, 06 Mar 2008 20:33:00 -0000	[thread overview]
Message-ID: <20080306203322.GA13983@caradoc.them.org> (raw)
In-Reply-To: <20071115192757.GA7557@caradoc.them.org>

On Thu, Nov 15, 2007 at 02:27:57PM -0500, Daniel Jacobowitz wrote:
> MontaVista builds both cross compilers (Linux or Windows -> MVL
> target) and native compilers (MVL host) on their Linux-based build
> systems.  We discovered that the two compilers disagreed on the
> size of long double for PowerPC.  Have I mentioned that I think
> making ABI choices based on configure tests is a really lousy idea?
> 
> This is the best I could think of to solve the problem.  Configure
> wants to grep through /usr/include; if we're building with $build
> != $host (and $host = $target is assured by the previous test, above
> the context of the diff), then ask GCC where glibc's headers are.
> 
> What do you think?  Is the approach OK?  How about the shell scripting
> choices?

Ping.  Patch is here:
  http://gcc.gnu.org/ml/gcc-patches/2007-11/msg00861.html

Mark asked whether we could remove the autodetection entirely, or
use it to AC_WARN instead of changing the ABI based on configure
tests.  I have no strong feeling about this, but while the check is
there I would like it to be more reliable.

-- 
Daniel Jacobowitz
CodeSourcery

  parent reply	other threads:[~2008-03-06 20:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15 20:18 Daniel Jacobowitz
2007-11-24 10:06 ` Mark Mitchell
2007-11-26  6:45   ` Daniel Jacobowitz
2007-11-26 21:09     ` Mark Mitchell
2008-03-06 20:33 ` Daniel Jacobowitz [this message]
2008-04-09  0:40   ` [ping] " Mark Mitchell
2008-04-09  2:59     ` David Edelsohn
2008-04-09  6:48       ` Mark Mitchell
2008-04-09 13:16         ` David Edelsohn
2008-04-09 13:37           ` Paolo Bonzini
2008-04-09 16:02           ` Mark Mitchell

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=20080306203322.GA13983@caradoc.them.org \
    --to=drow@false.org \
    --cc=gcc-patches@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).