public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: John Baldwin <jhb@FreeBSD.org>, Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3 2/3] Add an optional "alias" attribute to syscall entries.
Date: Wed, 28 Nov 2018 18:34:00 -0000	[thread overview]
Message-ID: <6b48a787-dec3-6be7-9a3d-7bb0284bc11c@redhat.com> (raw)
In-Reply-To: <24c28a03-e548-daac-1ad9-47d0f31eb13e@FreeBSD.org>

On 11/28/2018 06:00 PM, John Baldwin wrote:
> On 11/28/18 9:44 AM, Eli Zaretskii wrote:
>>> Cc: gdb-patches@sourceware.org
>>> From: John Baldwin <jhb@FreeBSD.org>
>>> Date: Wed, 28 Nov 2018 09:22:22 -0800
>>>
>>> Yes, I think this is better as well.  Eli, I don't know if other OS's will
>>> make use of this feature.  Given Pedro's new text above, do you think it
>>> should still be moved into a native section or should it stay in the the
>>> syscall section?
>>
>> I question the need to make this text more general than this feature
>> will ever become.  But if Pedro thinks we will have similar aliases on
>> other OSes, then sure, do it as Pedro suggests.

Don't other BSD kernels do something similar?

I think Linux always adds new syscalls under a new name, even if the
old replaced one is deprecated.

> Oh, I was just referring to Pedro's version being shorter.  I'm fine with
> moving it.  This is a bit longer as it restores a bit of the FreeBSD-specific
> note about syscall ABIs but that seemed relevant when moving it:
I'm fine with it as well.  It just felt like if the we could keep it short, it'd
avoid fragmenting the information.  IMO, a user reading the "catch syscall"
bits in the manual isn't going to remember to look up the FreeBSD-specific info
in a different node.  Unless we add some xrefs.

Thanks,
Pedro Alves

  parent reply	other threads:[~2018-11-28 18:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09 20:04 [PATCH v3 0/3] Update FreeBSD's syscall table John Baldwin
2018-11-09 20:04 ` [PATCH v3 2/3] Add an optional "alias" attribute to syscall entries John Baldwin
2018-11-09 20:18   ` Eli Zaretskii
2018-11-16 17:44     ` John Baldwin
2018-11-16 19:37       ` Eli Zaretskii
2018-11-27 17:13     ` Pedro Alves
2018-11-27 21:54       ` John Baldwin
2018-11-28  6:31         ` Eli Zaretskii
2018-11-28 12:19         ` Pedro Alves
2018-11-28 17:22           ` John Baldwin
2018-11-28 17:44             ` Eli Zaretskii
2018-11-28 18:00               ` John Baldwin
2018-11-28 18:31                 ` Eli Zaretskii
2018-11-28 18:34                 ` Pedro Alves [this message]
2018-11-28 19:15                   ` John Baldwin
2018-11-28 19:21                   ` Eli Zaretskii
2018-11-09 20:04 ` [PATCH v3 3/3] Update the FreeBSD system call table to match FreeBSD 12.0 John Baldwin
2018-11-09 20:04 ` [PATCH v3 1/3] Change get_syscalls_by_group to append to an existing vector of integers John Baldwin
2018-11-26 20:31 ` [PATCH v3 0/3] Update FreeBSD's syscall table John Baldwin
2018-11-27 17:20   ` Pedro Alves
2018-11-27 20:00     ` John Baldwin

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=6b48a787-dec3-6be7-9a3d-7bb0284bc11c@redhat.com \
    --to=palves@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jhb@FreeBSD.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).