mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Bobby Bingham <koorogi@koorogi.info>
To: musl@lists.openwall.com
Subject: Re: Deduplicating __NR_* and SYS_* syscall defines
Date: Wed, 11 May 2016 22:56:57 -0500	[thread overview]
Message-ID: <20160512035657.GB23989@dora.lan> (raw)
In-Reply-To: <20160512005712.GK21636@brightrain.aerifal.cx>

On Wed, May 11, 2016 at 08:57:12PM -0400, Rich Felker wrote:
> The p command just prints the pattern space. The trick is that we
> print it an extra time before the s command, but only if the line
> matches something the s command is going to change.
> 
> > Any objection to using Alexander's approach to avoid interleaving the
> > __NR_* and SYS_* lines?
> 
> I'm indifferent to the interleaving, but if we take that approach, we
> should make sure that the rules are written such that interrupting the
> make process between the commands doesn't leave a partial file that
> subsequent runs of make think is complete. It might be ok as-is if
> make automatically deletes the target on error producing it; otherwise
> we might need a temp file that's moved into place at the end. I always
> forge how this aspect of make works...

Make does what you want by default.

https://www.gnu.org/software/make/manual/html_node/Interrupts.html

> 
> > > > Same thing for this line in x32:
> > > > 
> > > >     #define __X32_SYSCALL_BIT        0x40000000
> > > 
> > > In general we've tried to eliminate this sort of macro and direct-code
> > > the values. I would be in favor of doing the same for x32 I think. But
> > > with my fixed sed command (above) I think that change is unnecssary
> > > and orthogonal to the deduplication.
> > 
> > I'll submit a separate patch to clean this up.
> 
> Any thoughts on how it should be done? If it were a clean decimal
> constant like on mips I'd just write each as a single integer literal
> (e.g. 6001, etc.) but since the syscall numbers are normally thought
> of as decimal whereas the x32 offset is hex/bit value, it seems + or |
> is still needed.

I agree.  I was planning to use +.

> 
> > > > I'm thinking something like the following awk script would work:
> > > > 
> > > >     {
> > > >         print
> > > >     }
> > > > 
> > > >     $1 ~ /^#(define|undef)$/ && $2 ~ /^__NR_/ {
> > > >         sub(/__NR_/, "SYS_", $2)
> > > >         print
> > > >     }
> > > > 
> > > > The handling for #undef is for the x32 file.  It looks like only the
> > > > `#undef __NR_getdents' in that file is actually necessary, and even that
> > > > could be avoided by just omitting the earlier line:
> > > > 
> > > >     #define __NR_getdents (__X32_SYSCALL_BIT + 78)
> > > 
> > > I don't see why any #undef is needed here; this looks like leftover
> > > cruft that was not properly cleaned up. All the logic for replacing
> > > syscall numbers belongs in src/internal/syscall.h or
> > > arch/$ARCH/syscall_arch.h, I think.
> > 
> > Ok.
> 
> Can you verify that removing these #undef-and-redefine lines from the
> bits header doesn't change the result (i.e. it's redundant with other
> files) for building libc?

I just verified, the generated code for libc is the same either way.

> 
> > > > So maybe we can get rid of the #undefs there, and simplify the awk script
> > > > accordingly.
> > > > 
> > > > Thoughts on this approach?  If this sounds ok, I'll submit a patch.
> > > 
> > > I'd rather use sed than awk if possible since it's more universally
> > > available and understood.
> > 
> > I must be the exception then :)
> 
> :-)
> 
> Rich


  reply	other threads:[~2016-05-12  3:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10  0:26 Bobby Bingham
2016-05-10  7:34 ` Alexander Monakov
2016-05-10  8:47   ` Alexander Monakov
2016-05-11 21:53 ` Rich Felker
2016-05-12  0:22   ` Bobby Bingham
2016-05-12  0:57     ` Rich Felker
2016-05-12  3:56       ` Bobby Bingham [this message]
2016-05-13 10:15       ` Szabolcs Nagy
2016-05-13 16:02         ` Rich Felker

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=20160512035657.GB23989@dora.lan \
    --to=koorogi@koorogi.info \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).