Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Cc: Doug Evans <dje@google.com>
Subject: [RFC] gnulib (was: Re: [RFA] lmemmem.patch)
Date: Mon, 31 Mar 2008 16:10:00 -0000	[thread overview]
Message-ID: <20080331160359.GA4003@caradoc.them.org> (raw)
In-Reply-To: <20080330213540.GA2856@caradoc.them.org>

On Sun, Mar 30, 2008 at 05:35:40PM -0400, Daniel Jacobowitz wrote:
> Here you go.  How does this look?  It frees us to rely on gnulib's
> stdint.h, string.h, and other useful modules should we want them.  I
> didn't make gdbserver completely use gnulib, only build memmem; I
> tested this on Linux (memmem present) and Windows (memmem missing).
> GDB will use the included memmem even on Linux, since glibc's is known
> to be slower.

A word of explanation is probably called for, since there wasn't much
context.

GDB runs on many platforms.  This calls for a certain amount of
portability goop to overcome their different limitations.  Right now,
this is handled mostly in libiberty.  One exception is gdb_stdint.h, which
comes from a macro in config.

A recent development on the portability scene is gnulib:
  http://www.gnu.org/software/gnulib/
There's an explanation of it on that page.  In summary, it's a
collection of source files and a script that can automatically copy
the necessary ones into your project or update existing copies
(gnulib-tool).  It's much larger and more active than libiberty
and it has both portability and general utility routines, e.g.
checksum algorithms and Unicode support.

Two other things I would like to use it for are stdint.h and
automatic line wrapping in error messages.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-03-31 16:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200803241737.m2OHbgC8016762@greed.delorie.com>
     [not found] ` <e394668d0803241050w6a1f341u585fb4906135a44b@mail.gmail.com>
     [not found]   ` <200803241758.m2OHwDid017265@greed.delorie.com>
     [not found]     ` <e394668d0803241333nedb753j9b7b1593c6d3989f@mail.gmail.com>
     [not found]       ` <20080324203738.GC29991@ins.uni-bonn.de>
     [not found]         ` <e394668d0803241346h5006b63du8997cf9e081dc907@mail.gmail.com>
     [not found]           ` <20080324205119.GE29991@ins.uni-bonn.de>
     [not found]             ` <e394668d0803241420w3db1813bj4aa7803b74f3d40b@mail.gmail.com>
     [not found]               ` <20080324212354.GA16323@caradoc.them.org>
     [not found]                 ` <e394668d0803241436w5160a2dfodd33d44b174cb9bf@mail.gmail.com>
2008-03-30 21:37                   ` [RFA] lmemmem.patch Daniel Jacobowitz
2008-03-31 16:10                     ` Daniel Jacobowitz [this message]
2008-03-31 18:35                     ` Doug Evans
2008-04-14 18:27                       ` Daniel Jacobowitz
2008-04-15 11:55                         ` Pierre Muller
2008-04-15 11:59                           ` Corinna Vinschen
2008-04-15 13:08                           ` 'Daniel Jacobowitz'
2008-04-15 13:15                             ` Pierre Muller
2008-04-15 13:37                               ` Corinna Vinschen
2008-04-15 14:12                                 ` Pierre Muller
2008-04-15 14:44                                   ` Corinna Vinschen
2008-04-15 14:57                                   ` Daniel Jacobowitz
2008-04-15 15:40                                     ` Pierre Muller
2008-04-15 17:14                                       ` 'Daniel Jacobowitz'
2008-04-15 18:07                                         ` Pierre Muller
2008-04-09 23:04                     ` Doug Evans
2008-04-10  5:31                       ` Daniel Jacobowitz

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=20080331160359.GA4003@caradoc.them.org \
    --to=drow@false.org \
    --cc=dje@google.com \
    --cc=gdb-patches@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