public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29746] ppoll() does not switch to __ppoll64 when -D_TIME_BITS=64 and -D_FORTIFY_SOURCE=2 is given on 32bit
Date: Thu, 03 Nov 2022 15:56:26 +0000 [thread overview]
Message-ID: <bug-29746-131-gr9hP0jzrr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29746-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29746
Andreas Schwab <schwab@linux-m68k.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|ppoll() does not switch to |ppoll() does not switch to
|__ppoll64 when |__ppoll64 when
|-D_TIME_BITS=64 and |-D_TIME_BITS=64 and
|-D_FORTIFY_SOURCE=2 is |-D_FORTIFY_SOURCE=2 is
|given on 33bit |given on 32bit
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-11-03 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 13:09 [Bug libc/29746] New: ppoll\ does not switch to __ppoll64 when -D_TIME_BITS=64 and -D_FORTIFY_SOURCE=2 is given on 33bit skabe at vega dot pgw.jp
2022-11-03 13:11 ` [Bug libc/29746] ppoll() " skabe at vega dot pgw.jp
2022-11-03 15:56 ` schwab@linux-m68k.org [this message]
2022-11-03 16:20 ` [Bug libc/29746] ppoll() does not switch to __ppoll64 when -D_TIME_BITS=64 and -D_FORTIFY_SOURCE=2 is given on 32bit adhemerval.zanella at linaro dot org
2022-11-08 16:46 ` adhemerval.zanella at linaro dot org
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=bug-29746-131-gr9hP0jzrr@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).