public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/15292] libgfortran depends on c99 functionality round and roundf
Date: Wed, 05 May 2004 13:24:00 -0000	[thread overview]
Message-ID: <20040505132421.25927.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040505091406.15292.rearnsha@gcc.gnu.org>


------- Additional Comments From rearnsha at gcc dot gnu dot org  2004-05-05 13:24 -------
Subject: Re:  libgfortran depends on c99 functionality
	round and roundf

On Wed, 2004-05-05 at 14:03, pinskia at gcc dot gnu dot org wrote:
> ------- Additional Comments From pinskia at gcc dot gnu dot org  2004-05-05 13:03 -------
> On more thing, why has the bug in netbsd for adding these functions, round and roundf been ignored.
> http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=24252
> In fact there is a patch in there to add them.

Well, it's more likely that it's just not been processed yet, there's
currently >3000 bugs outstanding.  I don't know what, if any, effort is
being put into making the C library C99 conforming [A quick search of
the mailing lists suggests that there is some activity, but it's
probably not an all-out push at this time].

Sadly NetBSD doesn't have as many folks triaging the bug database as GCC
does (and in some cases OS bugs are far harder to pin down, due to
subtle differences in HW).

In any case, that wouldn't affect NetBSD 1.6.x which is the last public
release.  Nor is it likely now to affect 2.0 when that comes out (since
the release branch has now been cut).

R.


-- 


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


  parent reply	other threads:[~2004-05-05 13:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-05  9:14 [Bug libfortran/15292] New: " rearnsha at gcc dot gnu dot org
2004-05-05 11:37 ` [Bug fortran/15292] " pinskia at gcc dot gnu dot org
2004-05-05 11:38 ` pinskia at gcc dot gnu dot org
2004-05-05 12:14 ` rearnsha at gcc dot gnu dot org
2004-05-05 12:43 ` pinskia at gcc dot gnu dot org
2004-05-05 12:45 ` rearnsha at gcc dot gnu dot org
2004-05-05 13:03 ` pinskia at gcc dot gnu dot org
2004-05-05 13:24 ` rearnsha at gcc dot gnu dot org [this message]
2004-05-30 16:22 ` [Bug libfortran/15292] " toon at moene dot indiv dot nluug dot nl
2004-06-12 17:59 ` cvs-commit at gcc dot gnu dot org
2004-06-12 18:01 ` pbrook at gcc dot gnu dot org
2004-06-14 17:27 ` cvs-commit 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=20040505132421.25927.qmail@sources.redhat.com \
    --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).