From: Robbie Harwood <rharwood@redhat.com>
To: Daniel Axtens <dja@axtens.net>, grub-devel@gnu.org
Subject: Re: [PATCH] Drop gnulib fix-base64.patch
Date: Tue, 23 Nov 2021 11:08:55 -0500 [thread overview]
Message-ID: <jlgr1b6dfc8.fsf@redhat.com> (raw)
In-Reply-To: <87wnkydgyk.fsf@dja-thinkpad.axtens.net>
[-- Attachment #1: Type: text/plain, Size: 834 bytes --]
Daniel Axtens <dja@axtens.net> writes:
> Robbie Harwood <rharwood@redhat.com> writes:
>
>> +/* For gnulib's base64 code. */
>> +#define _GL_ATTRIBUTE_CONST /* empty */
>
> Do we support any compiler so old or configuration so weird that we
> can't simply use 'const' here?
Unfortunately it's not quite that simple. _GL_ATTRIBUTE_CONST actually
gates turning on `__attribute ((__const__))`, which if memory serves is
a GCC extension. I don't know what the support matrix on grub is, but
based on the original patch there was a need to support non-gcc-likes.
Would be fine with changing that, though.
(Personally, I think it should be obvious to a reasonable compiler that
isbase64() is purely arithmetic. However, gnulib upstream did not like
my proposal to drop the attribute marker, so we're stuck with it.)
Be well,
--Robbie
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2021-11-23 16:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 19:22 [PATCH] Drop gnulib fix-base64.patch Robbie Harwood
2021-11-03 11:59 ` Darren Kenny
2021-11-14 9:36 ` Patrick Steinhardt
2021-11-23 15:33 ` Daniel Axtens
2021-11-23 16:08 ` Robbie Harwood [this message]
2021-11-23 17:20 ` Daniel Kiper
2021-11-24 14:36 ` Robbie Harwood
2021-11-25 17:09 ` Daniel Kiper
2021-11-29 23:21 ` Robbie Harwood
2021-11-30 16:33 ` Daniel Kiper
2021-12-07 20:34 ` Robbie Harwood
2021-12-09 14:46 ` Daniel Kiper
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=jlgr1b6dfc8.fsf@redhat.com \
--to=rharwood@redhat.com \
--cc=dja@axtens.net \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.