Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: System V IPC for psim try #2
Date: Mon, 17 Nov 2008 20:31:00 -0000	[thread overview]
Message-ID: <e394668d0811162303i69f4c787y4618dd4dc02fedbf@mail.gmail.com> (raw)
In-Reply-To: <491DA162.3030402@oarcorp.com>

On Fri, Nov 14, 2008 at 8:03 AM, Joel Sherrill
<joel.sherrill@oarcorp.com> wrote:
> Hi,
>
> I think I have taken Doug's comments into account
> with this revised version of the patch.  Hopefully
> it is ready to commit now.
>
> Comments appreciated.  Thanks.
>
> 2008-11-14  Joel Sherrill <joel.sherrill@oarcorp.com>
>
>       * Makefile.in, configure.ac, debug.c, debug.h, hw_sem.c, hw_shm.c:
>       Add support for System V shared memory and semaphores to PSIM where
>       available on the host.  Shared memory can be mapped into the
>       simulated processor's address space and protected using a semaphore.
>       * configure: Regenerated.

Hi.  Thanks for the making the changes.

nit: I think the convention is one *-line per file, though I see
sim/ppc/ChangeLog doesn't follow that rule precisely.  I like your
original changelog entry better (fwiw).

2008-09-08 Joel Sherrill <joel.sherrill@oarcorp.com>

 * configure: Regenerated.
 * configure.ac: Add test for System V shared memory and semaphore.
 * debug.c, debug.h: Add trace support for new devices.
 * hw_sem.c, hw_shm.c: New files.
 * Makefile.in: Add hw_sem.c and hw_shm.c.

Regarding:

+if test "$ac_cv_has_union_semun" = "yes"; then
+  AC_CACHE_CHECK(whether System V semaphores are supported,
+  ac_cv_sysv_sem,
+  [
+  AC_TRY_RUN(
+  [

Apologies for not noting this before.  I see ppc/configure.ac already
uses AC_TRY_RUN, so it's ok with me.  The problem with AC_TRY_RUN is
that it doesn't work in cross compilation environments.  In this case
all that will happen is that the sim won't support these extra
features so no big deal (And apologies if all of this has already gone
through your mind ... :-))


  reply	other threads:[~2008-11-17  7:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14 18:01 Joel Sherrill
2008-11-17 20:31 ` Doug Evans [this message]
2008-11-18 21:23   ` Joel Sherrill
2008-11-18 21:32     ` Doug Evans
2008-11-18 21:32       ` Joel Sherrill
2008-11-18 21:44         ` Daniel Jacobowitz
2008-11-19 12:41           ` Joel Sherrill

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=e394668d0811162303i69f4c787y4618dd4dc02fedbf@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=joel.sherrill@oarcorp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox