All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Zack Weinberg <zackw@panix.com>,
	mtk.manpages@gmail.com, linux-man@vger.kernel.org,
	libc-alpha@sourceware.org, Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: [PATCH] makecontext.3: Fix function declarator with empty parentheses.
Date: Fri, 5 Mar 2021 13:48:40 +0100	[thread overview]
Message-ID: <2b3d9f1d-287a-9747-0666-fb4d9331b494@gmail.com> (raw)
In-Reply-To: <8735x9hpe7.fsf@oldenburg.str.redhat.com>

Hi Florian,

On 3/5/21 11:21 AM, Florian Weimer wrote:
> * Alejandro Colomar:
>> Florian, should I file a bug in glibc's bugzilla?
> 
> I don't know.  SUSv2 has (void *func) (), which would make this a glibc
> bug.  I'm not sure if I have easy access to POSIX.1 from 2001, which I
> believe still has this function.
> 
> I am not sure if all glibc implementations of makecontext can be used to
> call variadic functions.

I reported the bug: <https://sourceware.org/bugzilla/show_bug.cgi?id=27523>

Thanks,

Alex

-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

      parent reply	other threads:[~2021-03-05 12:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04 19:45 [PATCH] makecontext.3: Fix function declarator with empty parentheses Alejandro Colomar
     [not found] ` <CAKCAbMg3G4EAeuUhN9EQTDnrTSD0sPoH0uH1=kkpfj9qYorPdg@mail.gmail.com>
2021-03-04 21:10   ` Florian Weimer
2021-03-05  1:13     ` Alejandro Colomar (man-pages)
2021-03-05 10:21       ` Florian Weimer
2021-03-05 10:27         ` Andreas Schwab
2021-03-05 12:48         ` Alejandro Colomar (man-pages) [this message]

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=2b3d9f1d-287a-9747-0666-fb4d9331b494@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=schwab@linux-m68k.org \
    --cc=zackw@panix.com \
    /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.