From: Mark Wielaard <mark@klomp.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Joseph Myers <josmyers@redhat.com>,
"Andreas K. Huettel" <dilfridge@gentoo.org>,
libc-alpha@sourceware.org
Subject: Re: [PATCH] v4: Use gcc __builtin_stdc_* builtins in stdbit.h if possible
Date: Thu, 1 Feb 2024 11:23:28 +0100 [thread overview]
Message-ID: <20240201102328.GB867@gnu.wildebeest.org> (raw)
In-Reply-To: <20240201101253.GA867@gnu.wildebeest.org>
On Thu, Feb 01, 2024 at 11:12:53AM +0100, Mark Wielaard wrote:
> On Mon, Jan 29, 2024 at 11:10:41PM +0100, Jakub Jelinek wrote:
> > diff --git a/manual/stdbit.texi b/manual/stdbit.texi
> > index fe41c671d8..8688930f12 100644
> > --- a/manual/stdbit.texi
> > +++ b/manual/stdbit.texi
> > @@ -32,7 +32,13 @@ and @code{unsigned long long int}. In addition, there is a
> > corresponding type-generic macro (not listed below), named the same as
> > the functions but without any suffix such as @samp{_uc}. The
> > type-generic macro can only be used with an argument of an unsigned
> > -integer type with a width of 8, 16, 32 or 64 bits.
> > +integer type with a width of 8, 16, 32 or 64 bits, or when using
> > +a compiler with support for
> > +@uref{https://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html@code{__builtin_stdc_bit_ceil}},
> > +etc.@:, built-in functions such as GCC 14.1 or later
> > +any unsigned integer type those built-in functions support.
> > +In GCC 14.1 that includes support for @code{unsigned __int128} and
> > +@code{unsigned _BitInt(@var{n})} if supported by the target.
> >
> > @deftypefun {unsigned int} stdc_leading_zeros_uc (unsigned char @var{x})
> > @deftypefunx {unsigned int} stdc_leading_zeros_us (unsigned short @var{x})
>
> make pdf didn't like that new @uref construct:
> https://builder.sourceware.org/buildbot/#/builders/264/builds/282
> https://builder.sourceware.org/buildbot/api/v2/logs/7481911/raw
>
> (/home/builder/shared/snapshots/worker/glibc-snapshots-trunk/glibc-build/glibc-
> dist/manual/stdbit.texi Chapter 21 [668]
> /home/builder/shared/snapshots/worker/glibc-snapshots-trunk/glibc-build/glibc-d
> ist/manual/stdbit.texi:37: Argument of @temp has an extra }.
> <inserted text>
> @par
> <to be read again>
> }
> @pdfurl ...btype /Link /A << /S /URI /URI (#1) >>}
> @endgroup
> @urefbreakfinish ...sh ->@unsepspaces @pdfurl {#1}
> @setbox 0 = @hbox {@ignore...
> l.37 ...iltins.html@code{__builtin_stdc_bit_ceil}}
> ,
> ?
> /home/builder/shared/snapshots/worker/glibc-snapshots-trunk/glibc-build/glibc-d
> ist/manual/stdbit.texi:37: Emergency stop.
> <inserted text>
> @par
> <to be read again>
> }
> @pdfurl ...btype /Link /A << /S /URI /URI (#1) >>}
> @endgroup
> @urefbreakfinish ...sh ->@unsepspaces @pdfurl {#1}
> @setbox 0 = @hbox {@ignore...
> l.37 ...iltins.html@code{__builtin_stdc_bit_ceil}}
> ,
> /home/builder/shared/snapshots/worker/glibc-snapshots-trunk/glibc-build/glibc-d
> ist/manual/stdbit.texi:37: ==> Fatal error occurred, no output PDF file produc
> ed!
>
> make info; make html; make dvi
> are all fine however.
But do note that the URL doesn't come out correctly even in the HTML
case:
https://snapshots.sourceware.org/glibc/trunk/latest/manual/libc.html#Bit-Manipulation
It shows and links to:
https://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html__builtin_stdc_bit_ceil
which should be:
https://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html#index-_005f_005fbuiltin_005fstdc_005fbit_005fceil
Cheers,
Mark
next prev parent reply other threads:[~2024-02-01 10:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 18:04 [PATCH] " Jakub Jelinek
2024-01-20 23:27 ` Joseph Myers
2024-01-22 9:19 ` [PATCH] v2: " Jakub Jelinek
2024-01-22 17:58 ` Joseph Myers
2024-01-26 10:12 ` [PATCH] v3: " Jakub Jelinek
2024-01-29 21:07 ` Joseph Myers
2024-01-29 21:18 ` Jakub Jelinek
2024-01-29 21:30 ` Joseph Myers
2024-01-29 22:10 ` [PATCH] v4: " Jakub Jelinek
2024-01-30 0:28 ` Andreas K. Huettel
2024-01-31 18:03 ` Joseph Myers
2024-02-01 10:12 ` Mark Wielaard
2024-02-01 10:23 ` Mark Wielaard [this message]
2024-02-01 10:33 ` [PATCH] Fix up stdbit.texi Jakub Jelinek
2024-02-01 11:05 ` Mark Wielaard
2024-02-01 14:42 ` Carlos O'Donell
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=20240201102328.GB867@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=dilfridge@gentoo.org \
--cc=jakub@redhat.com \
--cc=josmyers@redhat.com \
--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).