unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Mark Harris <mark.hsj@gmail.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org, DJ Delorie <dj@redhat.com>
Subject: Re: [PATCH v4] Always define __USE_TIME_BITS64 when 64 bit time_t is used
Date: Sat, 16 Mar 2024 02:04:03 -0700	[thread overview]
Message-ID: <CAMdZqKEdrq7jJdVzguzf4Gd7Sw7MQ3-mYaHFdc6_SjjrkjN23g@mail.gmail.com> (raw)
In-Reply-To: <20240315165737.2216661-1-adhemerval.zanella@linaro.org>

Adhemerval Zanella wrote:
> diff --git a/sysdeps/generic/features-time64.h b/sysdeps/generic/features-time64.h
> index 4d38b8ba76..0c5b74d631 100644
> --- a/sysdeps/generic/features-time64.h
> +++ b/sysdeps/generic/features-time64.h
> @@ -17,3 +17,7 @@
>     <https://www.gnu.org/licenses/>.  */
>
>  /* The generic configuration only support _TIME_BITS=32.  */
> +#define __USE_TIME_BITS64       0
> +/* The following macro defines whether the 64 time_t redirects will be
> +   used for 64 bit aware symbols.  */
> +#define __USE_TIME64_REDIRECTS  0

These macros are tested with #ifdef/#ifndef, so by defining them they
are enabled.  It looks like this generic header should be leaving
these undefined.

 - Mark

  parent reply	other threads:[~2024-03-16  9:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15 16:57 [PATCH v4] Always define __USE_TIME_BITS64 when 64 bit time_t is used Adhemerval Zanella
2024-03-15 21:33 ` DJ Delorie
2024-03-18 11:42   ` Adhemerval Zanella Netto
2024-03-16  9:04 ` Mark Harris [this message]
2024-03-18 11:21   ` Adhemerval Zanella Netto

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMdZqKEdrq7jJdVzguzf4Gd7Sw7MQ3-mYaHFdc6_SjjrkjN23g@mail.gmail.com \
    --to=mark.hsj@gmail.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=dj@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).