public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "espie at nerim dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/23356] FLT_EVAL_METHOD not defined on openbsd3.4
Date: Thu, 13 Oct 2005 11:12:00 -0000	[thread overview]
Message-ID: <20051013111157.11558.qmail@sourceware.org> (raw)
In-Reply-To: <bug-23356-10259@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from espie at nerim dot net  2005-10-13 11:11 -------
I added FLT_EVAL_METHOD to OpenBSD's math.h in january 2005.
Currently, all releases up to OpenBSD 3.5 have been discontinued.
OpenBSD 3.6 reaches end-of-life in a few months.

As far as OpenBSD is concerned, this bug is not important: neither 3.7,
nor 3.8, nor -current are affected.

It might bite some other system.

As far as I'm concerned, this is a generic issue with Linux-centric configure.
Everything is often set up to either assume no C99, or full C99 compliance, and
there are still systems in-between (to wit, libstdc++ all-or-nothing locale
approach).


-- 

espie at nerim dot net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |espie at nerim dot net


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23356


       reply	other threads:[~2005-10-13 11:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-23356-10259@http.gcc.gnu.org/bugzilla/>
2005-10-13 11:12 ` espie at nerim dot net [this message]
2005-11-17 18:34 ` fxcoudert at gcc dot gnu dot org
2005-08-12 17:08 [Bug libfortran/23356] New: " fxcoudert at gcc dot gnu dot org
2005-09-08 20:58 ` [Bug target/23356] " fxcoudert at gcc dot gnu dot 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=20051013111157.11558.qmail@sourceware.org \
    --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).