public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: gdb-patches@sourceware.org
Subject: [PATCH 1/5] gdb.threads/pthreads.c, K&R -> ANSI function style
Date: Wed, 20 Sep 2023 18:59:55 +0100	[thread overview]
Message-ID: <20230920175959.2305271-2-pedro@palves.net> (raw)
In-Reply-To: <20230920175959.2305271-1-pedro@palves.net>

gdb.threads/pthreads.c is declaring functions with old K&R style.
This commit converts them to ANSI style.

Change-Id: I1ce007c67bb4ab1e49248c014c7881e46634f8f8
---
 gdb/testsuite/gdb.threads/pthreads.c | 10 +++-------
 1 file changed, 3 insertions(+), 7 deletions(-)

diff --git a/gdb/testsuite/gdb.threads/pthreads.c b/gdb/testsuite/gdb.threads/pthreads.c
index fe1f89d0a23..7ec5604676f 100644
--- a/gdb/testsuite/gdb.threads/pthreads.c
+++ b/gdb/testsuite/gdb.threads/pthreads.c
@@ -27,8 +27,7 @@
 static int verbose = 0;
 
 static void
-common_routine (arg)
-     int arg;
+common_routine (int arg)
 {
   static int from_thread1;
   static int from_thread2;
@@ -90,8 +89,7 @@ thread2 (void * arg)
 }
 
 void
-foo (a, b, c)
-     int a, b, c;
+foo (int a, int b, int c)
 {
   int d, e, f;
 
@@ -99,9 +97,7 @@ foo (a, b, c)
 }
 
 int
-main(argc, argv)
-     int argc;
-     char **argv;
+main (int argc, char **argv)
 {
   pthread_t tid1, tid2;
   int j;
-- 
2.34.1


  reply	other threads:[~2023-09-20 18:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20 17:59 [PATCH 0/5] Adjust/fix gdb.thread/pthreads.exp for Cygwin Pedro Alves
2023-09-20 17:59 ` Pedro Alves [this message]
2023-09-20 17:59 ` [PATCH 2/5] Fix gdb.threads/pthreads.c formatting Pedro Alves
2023-09-20 17:59 ` [PATCH 3/5] Fix gdb.threads/pthreads.exp error handling/printing Pedro Alves
2023-09-20 17:59 ` [PATCH 4/5] In gdb.threads/pthreads.c, handle pthread_attr_setscope ENOTSUP Pedro Alves
2023-09-20 17:59 ` [PATCH 5/5] Adjust gdb.thread/pthreads.exp for Cygwin Pedro Alves
2023-09-21 19:21 ` [PATCH 0/5] Adjust/fix " Tom Tromey

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=20230920175959.2305271-2-pedro@palves.net \
    --to=pedro@palves.net \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).