public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: Libiberty: POSIXify psignal definition
Date: Thu, 05 May 2011 07:39:00 -0000	[thread overview]
Message-ID: <20110505073039.GA23122@calimero.vinschen.de> (raw)

[Please keep me CCed, I'm not subscribed to gcc-patches.  Thank you]

Hi,

the definition of psignal in libiberty is

   void psignal (int, char *);

The correct definition per POSIX is

   void psignal (int, const char *);

The below patch fixes that.


Thanks,
Corinna


	* strsignal.c (psignal): Change second parameter to const char *.
	Fix comment accordingly.


Index: strsignal.c
===================================================================
RCS file: /cvs/src/src/libiberty/strsignal.c,v
retrieving revision 1.11
diff -u -p -r1.11 strsignal.c
--- strsignal.c	19 Jun 2008 15:17:56 -0000	1.11
+++ strsignal.c	5 May 2011 07:29:42 -0000
@@ -538,7 +538,7 @@ strtosigno (const char *name)
 
 /*
 
-@deftypefn Supplemental void psignal (int @var{signo}, char *@var{message})
+@deftypefn Supplemental void psignal (int @var{signo}, const char *@var{message})
 
 Print @var{message} to the standard error, followed by a colon,
 followed by the description of the signal specified by @var{signo},
@@ -551,7 +551,7 @@ followed by a newline.
 #ifndef HAVE_PSIGNAL
 
 void
-psignal (int signo, char *message)
+psignal (int signo, const char *message)
 {
   if (signal_names == NULL)
     {


-- 
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat

             reply	other threads:[~2011-05-05  7:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05  7:39 Corinna Vinschen [this message]
2011-05-05  7:55 ` Andrew Pinski
2011-05-05  9:00   ` Corinna Vinschen
2011-05-05 17:32     ` Andrew Pinski
2011-05-17 18:28 ` Richard Earnshaw
2011-05-17 18:32   ` DJ Delorie
2011-05-17 19:34     ` Richard Earnshaw
2011-05-17 19:47       ` Corinna Vinschen
2011-05-18  0:15         ` DJ Delorie
2011-05-18 18:38           ` Richard Earnshaw
2011-05-18 19:05             ` DJ Delorie
2011-05-18 19:27               ` Corinna Vinschen
2011-05-18 20:19               ` Joseph S. Myers
2011-05-18 20:26                 ` DJ Delorie
2011-05-18 20:31                   ` Joseph S. Myers
2011-05-26 16:46                 ` DJ Delorie
2011-06-08 12:21                   ` Hans-Peter Nilsson
2011-06-08 13:12                     ` Richard Earnshaw
2011-06-08 14:09                     ` DJ Delorie
2011-06-20 16:57                 ` Removing target-libiberty (was: Re: Libiberty: POSIXify psignal definition) Hans-Peter Nilsson
2011-06-20 17:03                   ` Joseph S. Myers
2011-06-22 18:44                     ` Hans-Peter Nilsson
2011-06-22 19:37                       ` DJ Delorie
2011-06-22 21:40                       ` Hans-Peter Nilsson
2011-05-17 20:03       ` Libiberty: POSIXify psignal definition DJ Delorie
2011-05-17 19:42   ` Corinna Vinschen
2011-05-17 21:23     ` DJ Delorie

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=20110505073039.GA23122@calimero.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=gcc-patches@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).