public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: "François-Xavier Coudert" <fxcoudert@gmail.com>
Cc: gcc@gcc.gnu.org,  gfortran <fortran@gcc.gnu.org>
Subject: Re: gfortran and -mlong-double-128
Date: Thu, 16 Feb 2006 15:17:00 -0000	[thread overview]
Message-ID: <200602161517.24425.paul@codesourcery.com> (raw)
In-Reply-To: <19c433eb0602160714h3e664a48qc20a723c59c74bba@mail.gmail.com>

On Thursday 16 February 2006 15:14, François-Xavier Coudert wrote:
> > Having gfortran magically know about certain ABI breaking options, and
> > doing funny things on certain targets seems a very bad precedent to me.
>
> Then, I think we should have the front-end refuse the option. It's
> annoying to have a compiler accept code, and only tell you at runtime
> (at the end of your simulation!) that it can't work.

The only thing that can do that is the driver (probably via spec strings). The 
compiler itself doesn't know what multilibs you have available.

Paul

  reply	other threads:[~2006-02-16 15:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-16 11:09 François-Xavier Coudert
2006-02-16 12:50 ` Richard Guenther
2006-02-16 12:57   ` François-Xavier Coudert
2006-02-16 14:11     ` Jakub Jelinek
2006-02-16 15:17       ` Richard Guenther
2006-02-16 15:04 ` Paul Brook
2006-02-16 15:14   ` François-Xavier Coudert
2006-02-16 15:17     ` Paul Brook [this message]
2006-02-16 15:19   ` Richard Guenther
2006-02-16 15:24     ` Andrew Pinski
2006-02-16 15:28     ` Paul Brook
2006-02-16 15:48       ` Jakub Jelinek

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=200602161517.24425.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=fortran@gcc.gnu.org \
    --cc=fxcoudert@gmail.com \
    --cc=gcc@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).