From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 85880 invoked by alias); 15 Mar 2018 10:18:10 -0000 Mailing-List: contact fortran-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: fortran-owner@gcc.gnu.org Received: (qmail 85857 invoked by uid 89); 15 Mar 2018 10:18:09 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy= X-Spam-User: qpsmtpd, 2 recipients X-HELO: mail-it0-f66.google.com Received: from mail-it0-f66.google.com (HELO mail-it0-f66.google.com) (209.85.214.66) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 15 Mar 2018 10:18:08 +0000 Received: by mail-it0-f66.google.com with SMTP id w3-v6so8387031itc.4; Thu, 15 Mar 2018 03:18:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=aD8oIDeoaLZuFm6fVU1FK30e8sPXU7pIJvL4mKm2jiQ=; b=DCcktU0zWOFung6Q49UME5NRttqZNGlKHX7sk6EGSgTxN2/37ZgPYOTUnSAnqNt89Y 5wL3acfppQF3Nj5y3FkUD4CpVtDDB/V6Gr7ALvgmGTbwAgy82EN6qWuyuzjOGqt8fZ4d idva+yjUkno4HY6zh9xj0KxvWQoql01YNWwtVBUCfP5eNl9I1vtty/v7QCkVCWB1ysty iCNyQfhuV1aTGjOPRrcEN0/iUraDK/xZEssob2SkhRji3jaQaNwaK2C/nNp7RP0xWc5v KcHIWhiKceVxGNsrEdU+O1Lr2pkpIhN6Cm2In0AXYn9Gnjtx2RiGJrc95p7l288afRO7 i06g== X-Gm-Message-State: AElRT7EdKpFjTa0Y+VEJywRRaNSp+g0MK/mt3kY9ici+NoazpTp8+UEi qaqhEg7iDh19heb+IOfIlXvpT6xTHuHGa3YEuY0= X-Google-Smtp-Source: AG47ELtq4aO0ViOjkgjaHQLw3W7klC82wuo2ubH8dPw8xshNknGJ6N5lNqoZHauYvXDUloQDjxzJANCBuSl5z4bIlIs= X-Received: by 10.36.217.138 with SMTP id p132mr5756719itg.41.1521109086570; Thu, 15 Mar 2018 03:18:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.2.30.221 with HTTP; Thu, 15 Mar 2018 03:18:06 -0700 (PDT) In-Reply-To: <20180314005722.GA43280@troutmask.apl.washington.edu> References: <20180311165209.GA60279@troutmask.apl.washington.edu> <20180311204239.GA56613@troutmask.apl.washington.edu> <20180312173706.GB61632@troutmask.apl.washington.edu> <20180313040809.GA69151@troutmask.apl.washington.edu> <20180314005722.GA43280@troutmask.apl.washington.edu> From: "Bin.Cheng" Date: Thu, 15 Mar 2018 10:18:00 -0000 Message-ID: Subject: Re: [PATCH] Fortran -- clean up KILL To: sgk@troutmask.apl.washington.edu Cc: Janne Blomqvist , Fortran List , GCC Patches Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2018-03/txt/msg00057.txt.bz2 On Wed, Mar 14, 2018 at 12:57 AM, Steve Kargl wrote: > On Tue, Mar 13, 2018 at 09:49:10PM +0200, Janne Blomqvist wrote: >> >> int val = kill (pid, signal); >> return (val == 0): 0 ? errno; >> >> like it already does for the optional status argument for kill_sub. >> > > Committed as r258511 with your suggested change. Hi Steve, After this change, AArch64/arm bare-metal cross (fortran) toolchain fail to build with below error message: /.../obj/gcc2/./gcc/xgcc -B/.../obj/gcc2/./gcc/ -B/.../install/aarch64-none-elf/bin/ -B/.../install/aarch64-none-elf/lib/ -isystem /.../install/aarch64-none-elf/include -isystem /.../install/aarch64-none-elf/sys-include -DHAVE_CONFIG_H -I. -I/.../gcc/libgfortran -iquote/.../gcc/libgfortran/io -I/.../gcc/libgfortran/../gcc -I/.../gcc/libgfortran/../gcc/config -I../../.././gcc -I/.../gcc/libgfortran/../libgcc -I../../libgcc -I/.../gcc/libgfortran/../libbacktrace -I../../libbacktrace -I../libbacktrace -std=gnu11 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wextra -Wwrite-strings -Werror=implicit-function-declaration -Werror=vla -fcx-fortran-rules -ffunction-sections -fdata-sections -g -ffunction-sections -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); ^~~~ In file included from /.../gcc/libgfortran/intrinsics/kill.c:26: /.../gcc/libgfortran/intrinsics/kill.c:55:14: error: conflicting types for 'kill' export_proto(kill); ^~~~ /.../gcc/libgfortran/libgfortran.h:150:57: note: in definition of macro 'sym_rename2' #define sym_rename2(old, ulp, new) extern __typeof(old) old __asm__(#ulp #new) ^~~ /.../gcc/libgfortran/libgfortran.h:148:30: note: in expansion of macro 'sym_rename1' #define sym_rename(old, new) sym_rename1(old, __USER_LABEL_PREFIX__, new) ^~~~~~~~~~~ /.../gcc/libgfortran/libgfortran.h:195:26: note: in expansion of macro 'sym_rename' # define export_proto(x) sym_rename(x, PREFIX(x)) ^~~~~~~~~~ /.../gcc/libgfortran/intrinsics/kill.c:55:1: note: in expansion of macro 'export_proto' export_proto(kill); ^~~~~~~~~~~~ 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); ^~~~ /.../gcc/libgfortran/intrinsics/kill.c:58:1: error: conflicting types for 'kill' kill (GFC_INTEGER_4 pid, GFC_INTEGER_4 signal) ^~~~ 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); ^~~~ The gcc is configured with: gcc/configure --target=aarch64-none-elf --prefix=... --with-gmp=.../host-tools --with-mpfr=.../host-tools --with-mpc=.../host-tools --with-isl=.../host-tools --with-pkgversion=unknown --disable-shared --disable-nls --disable-threads --disable-tls --enable-checking=yes --enable-languages=c,c++ --with-newlib --enable-languages=c,c++,fortran I don't know fortran, so any suggestion how to fix this? Note that -mabi=ilp32 is required to reproduce the breakage. Thanks, bin > > -- > Steve