From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: "Bin.Cheng" <amker.cheng@gmail.com>
Cc: Janne Blomqvist <blomqvist.janne@gmail.com>,
Fortran List <fortran@gcc.gnu.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fortran -- clean up KILL
Date: Thu, 15 Mar 2018 15:07:00 -0000 [thread overview]
Message-ID: <20180315150659.GA61934@troutmask.apl.washington.edu> (raw)
In-Reply-To: <CAHFci29uqvNAM1zSvhNfii4TeDHyxeq0XPsD_DdQLXv0JXkr1w@mail.gmail.com>
On Thu, Mar 15, 2018 at 12:20:08PM +0000, Bin.Cheng wrote:
> >> -fdata-sections -O2 -mabi=ilp32 -MT kill.lo -MD -MP -MF .deps/kill.Tpo
> >> -c /.../gcc/libgfortran/intrinsics/kill.c -o kill.o
> >> /.../gcc/libgfortran/intrinsics/kill.c:54:22: error: conflicting types
> >> for 'kill'
> >> extern GFC_INTEGER_4 kill (GFC_INTEGER_4, GFC_INTEGER_4);
> >> ^~~~
> >> In file included from /.../install/aarch64-none-elf/include/signal.h:6,
> >> from /.../gcc/libgfortran/intrinsics/kill.c:28:
> >> /.../install/aarch64-none-elf/include/sys/signal.h:176:5: note:
> >> previous declaration of 'kill' was here
> >> int kill (pid_t, int);
> >> ^~~~
Does this fix the issue for you?
Index: libgfortran/intrinsics/kill.c
===================================================================
--- libgfortran/intrinsics/kill.c (revision 258537)
+++ libgfortran/intrinsics/kill.c (working copy)
@@ -36,11 +36,9 @@ see the files COPYING3 and COPYING.RUNTIME respectivel
INTEGER, INTENT(IN) :: PID, SIGNAL */
#ifdef HAVE_KILL
-extern void kill_sub (GFC_INTEGER_4, GFC_INTEGER_4, GFC_INTEGER_4 *);
-iexport_proto(kill_sub);
void
-kill_sub (GFC_INTEGER_4 pid, GFC_INTEGER_4 signal, GFC_INTEGER_4 *status)
+_gfortran_kill_sub (GFC_INTEGER_4 pid, GFC_INTEGER_4 signal, GFC_INTEGER_4 *status)
{
int val;
@@ -49,13 +47,9 @@ kill_sub (GFC_INTEGER_4 pid, GFC_INTEGER_4 signal, GFC
if (status != NULL)
*status = (val == 0) ? 0 : errno;
}
-iexport(kill_sub);
-extern GFC_INTEGER_4 kill (GFC_INTEGER_4, GFC_INTEGER_4);
-export_proto(kill);
-
GFC_INTEGER_4
-kill (GFC_INTEGER_4 pid, GFC_INTEGER_4 signal)
+_gfortran_kill (GFC_INTEGER_4 pid, GFC_INTEGER_4 signal)
{
int val;
val = (int)kill (pid, signal);
--
Steve
20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4
20161221 https://www.youtube.com/watch?v=IbCHE-hONow
next prev parent reply other threads:[~2018-03-15 15:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 16:52 Steve Kargl
2018-03-11 20:16 ` Janne Blomqvist
2018-03-11 20:42 ` Steve Kargl
2018-03-12 16:56 ` Janne Blomqvist
2018-03-12 17:37 ` Steve Kargl
2018-03-12 19:05 ` Janne Blomqvist
2018-03-13 4:08 ` Steve Kargl
2018-03-13 19:49 ` Janne Blomqvist
2018-03-14 0:57 ` Steve Kargl
2018-03-15 10:18 ` Bin.Cheng
2018-03-15 12:11 ` Bin.Cheng
2018-03-15 12:20 ` Bin.Cheng
2018-03-15 15:07 ` Steve Kargl [this message]
2018-03-15 12:35 ` Richard Biener
2018-03-15 14:10 ` Steve Kargl
2018-03-15 16:35 ` Jakub Jelinek
2018-03-15 15:45 ` Bin.Cheng
2018-03-15 17:35 ` Jakub Jelinek
2018-03-15 15:57 ` Bin.Cheng
2018-03-15 16:28 ` Steve Kargl
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=20180315150659.GA61934@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=amker.cheng@gmail.com \
--cc=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--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).