public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] stdio: Move include of bits/stdio-ldbl.h before bits/stdio.h
Date: Sat, 22 Jan 2022 11:39:01 +0100	[thread overview]
Message-ID: <aed9bf69-7122-513b-f806-2807cd43311d@physik.fu-berlin.de> (raw)
In-Reply-To: <9dedf9b9-5af3-3f3b-e749-2c8e50ec5dc4@linaro.org>

Hi Adhemerval!

On 3/23/21 18:59, Adhemerval Zanella wrote:
> I am not sure if this is the correct approach, I am seeing it building for powerpc64le with gcc version 10.2.1 20210126:
> 
> | powerpc64le-glibc-linux-gnu-gcc nscd.c -c [...]
> | In file included from ../include/sys/cdefs.h:3,
> |                  from ../include/features.h:484,
> |                  from ../sysdeps/powerpc/bits/floatn.h:22,
> |                  from ../include/stdio.h:7,
> |                  from ../argp/argp.h:23,
> |                  from ../include/argp.h:2,
> |                  from nscd.c:20:
> | ../misc/sys/cdefs.h:503:20: error: ‘__dprintf_chk’ undeclared here (not in a function); did you mean ‘__sprintf_chk’?
> |   503 |   extern __typeof (__##name) __##name \
>       |                    ^~
> | ../libio/bits/stdio-ldbl.h:98:1: note: in expansion of macro ‘__LDBL_REDIR2_DECL’
> |    98 | __LDBL_REDIR2_DECL (dprintf_chk)
> |       | ^~~~~~~~~~~~~~~~~~
> | [...]
> 
> The postprocessor output shows:
> 
> | [...]
> |  2820 extern __typeof (__dprintf_chk) __dprintf_chk __asm ("" "__" "dprintf_chk" "ieee128");
> | [...]
> |  3067 extern int __dprintf_chk (int __fd, int __flag, const char *__restrict __fmt,
> | 3068      ...) __attribute__ ((__format__ (__printf__, 3, 4)));
> 
> Meaning we are not using __typeof *before* the function prototype
> is define.
> 
> I think to proper handle this LLVM limitation we will need to fully
> rework how __LDBL_REDIR2_DECL does the redirect by something similar
> to what __REDIRECT does by defining something like:
> 
> | #if __LDOUBLE_REDIRECTS_TO_FLOAT128_ABI == 1
> | # ifdef __REDIRECT
> |
> | /* Alias name defined automatically.  */
> | #  define __LDBL_REDIR(name, proto) \
> |  extern name proto __asm__ (__ASMNAME ("__" #name "ieee128"));
> |
> | /* Alias name defined automatically, with leading underscores.  */
> | #  define __LDBL_REDIR2_DECL(name) \
> |    extern __##name proto __asm__ (__ASMNAME ("__" #name "ieee128"));
> 
> |
> | /* Alias name defined manually.  */
> | #  define __LDBL_REDIR1(name, proto, alias) \
> |  extern name proto __asm__ (__ASMNAME (alias));
> 
> And replace __LDBL_REDIR_DECL with __LDBL_REDIR and __LDBL_REDIR1_DECL
> with __LDBL_REDIR1 (while adding the require argument prototype).  It
> will allow to move the stdio-ldbl.h definitions to stdio and remove the
> header.

Do you think you could create a patch for me to test? I think you would be
faster in getting it right. The sparc64 porterbox gcc202 is available for
testing.

The underlying bug [1] is still present in glibc 2.33. I just ran into it
again.

Adrian

> [1] https://sourceware.org/bugzilla/show_bug.cgi?id=27558

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


  parent reply	other threads:[~2022-01-22 10:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-22 11:15 John Paul Adrian Glaubitz
2021-03-23 17:59 ` Adhemerval Zanella
2021-08-16 12:24   ` John Paul Adrian Glaubitz
2022-01-22 10:39   ` John Paul Adrian Glaubitz [this message]
2022-02-23 20:51   ` John Paul Adrian Glaubitz
2022-02-24 17:10     ` Adhemerval Zanella
2022-03-03 19:25       ` Adhemerval Zanella
2022-03-08 10:34         ` John Paul Adrian Glaubitz

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=aed9bf69-7122-513b-f806-2807cd43311d@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@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).