public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Alejandro Colomar via Libc-alpha <libc-alpha@sourceware.org>
Cc: Alejandro Colomar <alx@kernel.org>,
	 Xi Ruoyao <xry111@xry111.site>, Sam James <sam@gentoo.org>,
	 Richard Biener <rguenth@gcc.gnu.org>,
	Andrew Pinski <apinski@marvell.com>
Subject: Re: [RFC v1 0/2] Use -fno-delete-null-pointer-checks to build glibc
Date: Tue, 11 Jul 2023 15:18:51 +0200	[thread overview]
Message-ID: <87a5w2bn7o.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20230711131105.19203-1-alx@kernel.org> (Alejandro Colomar via Libc-alpha's message of "Tue, 11 Jul 2023 15:11:04 +0200")

* Alejandro Colomar via Libc-alpha:

> In file included from ../include/sys/cdefs.h:10,
>                  from ../include/features.h:503,
>                  from ../assert/assert.h:35,
>                  from ../include/assert.h:1,
>                  from gconv_conf.c:19:
> ../include/dirent.h:53:17: error: expected ‘)’ before numeric constant
>    53 |      __nonnull (4) attribute_hidden;
>       |                 ^

This is a typo, it should be __nonnull ((4)).

The __nonnull redefinition simply hides it for now.

Thanks,
Florian


  parent reply	other threads:[~2023-07-11 13:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11 13:11 Alejandro Colomar
2023-07-11 13:11 ` [RFC v1 1/2] Makeconfig: Use one line per token Alejandro Colomar
2023-07-11 18:05   ` Adhemerval Zanella Netto
2023-07-11 13:11 ` [RFC v1 2/2] Makeconfig: Compile glibc with -fno-delete-null-pointer-checks Alejandro Colomar
2023-07-11 13:41   ` Florian Weimer
2023-07-11 13:53     ` Siddhesh Poyarekar
2023-07-12 10:56   ` Richard Biener
2023-07-12 12:22     ` Cristian Rodríguez
2023-07-12 12:43     ` Florian Weimer
2023-07-11 13:18 ` Florian Weimer [this message]
2023-07-11 13:19   ` [RFC v1 0/2] Use -fno-delete-null-pointer-checks to build glibc Alejandro Colomar
2023-07-11 13:22 ` Xi Ruoyao
2023-07-11 13:24   ` Alejandro Colomar

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=87a5w2bn7o.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=alx@kernel.org \
    --cc=apinski@marvell.com \
    --cc=libc-alpha@sourceware.org \
    --cc=rguenth@gcc.gnu.org \
    --cc=sam@gentoo.org \
    --cc=xry111@xry111.site \
    /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).