Linux DTrace development list
 help / color / mirror / Atom feed
From: Nick Alcock <nick.alcock@oracle.com>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: Nick Alcock <nick.alcock@oracle.com>,
	dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [DTrace-devel] [PATCH v2 2/2] dlibs: pregenerated translators for 6.10
Date: Wed, 19 Jun 2024 14:23:30 +0100	[thread overview]
Message-ID: <875xu5awx9.fsf@esperi.org.uk> (raw)
In-Reply-To: <1d036253-cd7e-4ee4-8a48-ef751e7c8a34@oracle.com> (Alan Maguire's message of "Fri, 14 Jun 2024 13:25:05 +0100")

On 14 Jun 2024, Alan Maguire spake thusly:

> On 13/06/2024 13:22, Alan Maguire wrote:
>> On 07/06/2024 19:41, Nick Alcock via DTrace-devel wrote:
>>> All differences from the previous translators (6.1) are no-effect
>>> ordering changes other than those one would expect from the changes to
>>> the .d files.
>>>
>>> Signed-off-by: Nick Alcock <nick.alcock@oracle.com>
>> 
>> 
>> I hit the issue with the disappearing bd_partno field in io.d on 6.10 so
>> this is great!
>> 
>> nit: I guess defining
>> 
>> inline int dev_partno[struct block_device *B] = B->__bd_flags.counter &
>> 0xff;
>> 
>> ...might reduce complexity of some of the statements in io.d
>>
>
> sorry, ignore this I missed the handling in patch 1..

Yeah this is all generated code -- and the advantage of doing this in M4
is that it means we can do things like this even where variables aren't
allowed, because the D parser never knows.

Downside: it means dealing with M4, which is a deeply lovely language
which we should be using for everything right about the time we rewrite
the Linux kernel in Befunge.

  reply	other threads:[~2024-06-19 13:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07 18:41 [PATCH v2 1/2] translators: support 6.10 Nick Alcock
2024-06-07 18:41 ` [PATCH v2 2/2] dlibs: pregenerated translators for 6.10 Nick Alcock
2024-06-13 12:22   ` [DTrace-devel] " Alan Maguire
2024-06-14 12:25     ` Alan Maguire
2024-06-19 13:23       ` Nick Alcock [this message]
2024-06-19  3:32 ` [PATCH v2 1/2] translators: support 6.10 Kris Van Hees
2024-06-19 12:41   ` Nick Alcock
2024-06-19 13:15   ` Nick Alcock
2024-06-20 17:54     ` Kris Van Hees
2024-06-19 13:21 ` [PATCH v3] " Nick Alcock
2024-06-20 17:55   ` Kris Van Hees

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=875xu5awx9.fsf@esperi.org.uk \
    --to=nick.alcock@oracle.com \
    --cc=alan.maguire@oracle.com \
    --cc=dtrace-devel@oss.oracle.com \
    --cc=dtrace@lists.linux.dev \
    /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