qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: renzo@cs.unibo.it (Renzo Davoli)
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] cvs cpu-exec.c (bug?)
Date: Sat, 10 Jul 2004 23:46:25 +0200	[thread overview]
Message-ID: <20040710214625.GB1838@cs.unibo.it> (raw)
In-Reply-To: <40F00124.5010902@bellard.org>

I have just returned from a conference and I have just checked out the
latest version from the cvs.

My compiler refused to compile the cpu-exec.c without the following
trivial patch, in line 906:

<int cpu_signal_handler(int host_signum, siginfo *info,
<                       void *puc)
>int cpu_signal_handler(int host_signum, struct siginfo *info,
>                       void *puc)

the keyword "struct" is missing defining the argument named info.
Maybe several other compilers have the implicit typedef on structs and
give either no error or just a warning.

For the sake of portability (and consistency, siginfo is always named as
"struct" in the remaining of the code) I feel it should be better to fix
it.

Thanks. Ciao.
		renzo

  parent reply	other threads:[~2004-07-10 21:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-09 23:18 [Qemu-devel] openbsd image on freeoszoo Jim C. Brown
2004-07-10  1:27 ` [Qemu-devel] " Jim C. Brown
2004-07-10 12:00   ` Julian Seward
2004-07-10 15:16     ` Jim C. Brown
2004-07-10 14:45   ` Fabrice Bellard
2004-07-10 20:52     ` Jim C. Brown
2004-07-10 21:46     ` Renzo Davoli [this message]
2004-07-10 22:23     ` Julian Seward
2004-07-11  0:52       ` Jim C. Brown
2004-07-12 12:12         ` Julian Seward
2004-07-10  7:50 ` [Qemu-devel] " Raphaël Enrici
2004-07-11  0:16 ` Stefano Marinelli
2004-07-11  0:53   ` Jim C. Brown
2004-07-11  7:22     ` Stefano Marinelli

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=20040710214625.GB1838@cs.unibo.it \
    --to=renzo@cs.unibo.it \
    --cc=qemu-devel@nongnu.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 NNTP newsgroup(s).