public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carlos at codesourcery dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/10103] Targets defining __NO_LONG_DOUBLE_MATH should still have *l prototypes in headers. Date: Mon, 27 Apr 2009 17:01:00 -0000 [thread overview] Message-ID: <20090427170127.8251.qmail@sourceware.org> (raw) In-Reply-To: <20090424202955.10103.carlos@codesourcery.com> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 792 bytes --] ------- Additional Comments From carlos at codesourcery dot com 2009-04-27 17:01 ------- I tested the following patch on hppa: http://sources.redhat.com/ml/libc-hacker/2009-04/msg00004.html No regressions. However, I don't see the long double prototypes. The port sets __NO_LONG_DOUBLE_MATH set to 1, and I verified this. The build sets NO_LONG_DOUBLE to 1 because the port sets long-double-fcts = no. Compiling test-ldouble.c with -Werror fails because of the missing prototypes. math/libm-test.c:5446: warning: implicit declaration of function scalbl math/libm-test.c: In function scalbn_test: -- http://sourceware.org/bugzilla/show_bug.cgi?id=10103 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2009-04-27 17:01 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-24 20:30 [Bug libc/10103] New: " carlos at codesourcery dot com 2009-04-24 20:32 ` [Bug libc/10103] " carlos at codesourcery dot com 2009-04-24 20:36 ` jakub at redhat dot com 2009-04-27 17:01 ` carlos at codesourcery dot com [this message] [not found] <bug-10103-131@http.sourceware.org/bugzilla/> 2011-11-04 14:25 ` schwab@linux-m68k.org 2014-06-30 9:18 ` fweimer at redhat dot com
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=20090427170127.8251.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.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: linkBe 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).