public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jaak at ristioja dot ee" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/16459] New: endian.h does not define byte-order conversion functions
Date: Thu, 16 Jan 2014 12:52:00 -0000	[thread overview]
Message-ID: <bug-16459-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=16459

            Bug ID: 16459
           Summary: endian.h does not define byte-order conversion
                    functions
           Product: glibc
           Version: 2.17
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: jaak at ristioja dot ee
                CC: drepper.fsp at gmail dot com

"man 3 endian" says it does, but actually it doesn't. If it would, one would be
able to take the address of such a function:

  #define _BSD_SOURCE
  #include <endian.h>

  void g() {
    uint64_t (*f)(uint64_t) = &htole64;
  }

$ gcc -Wimplicit-function-declaration test2.c -c
test.c: In function 'g':
test.c:5:3: warning: implicit declaration of function 'uint64_t'
[-Wimplicit-function-declaration]
test.c:5:14: error: 'f' undeclared (first use in this function)
test.c:5:14: note: each undeclared identifier is reported only once for each
function it appears in
test.c:5:30: error: 'htole64' undeclared (first use in this function)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2014-01-16 12:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 12:52 jaak at ristioja dot ee [this message]
2014-01-16 19:01 ` [Bug libc/16459] " joseph at codesourcery dot com
2014-01-16 19:49 ` jaak at ristioja dot ee
2014-01-16 20:50   ` Ondřej Bílka
2014-01-16 20:51 ` neleai at seznam dot cz
2014-06-13  8:55 ` 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=bug-16459-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).