public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vvinayag at arm dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/26647] New: [-Werror=array-parameter=] due to different declarations for __sigsetjmp
Date: Tue, 22 Sep 2020 13:07:16 +0000	[thread overview]
Message-ID: <bug-26647-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=26647

            Bug ID: 26647
           Summary: [-Werror=array-parameter=] due to different
                    declarations for __sigsetjmp
           Product: glibc
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: vvinayag at arm dot com
                CC: carlos at redhat dot com
  Target Milestone: ---

After this patch [1], I am seeing this -Warray-parameter error when building
gcc:

In file included from ../include/pthread.h:1,
                 from ../sysdeps/nptl/thread_db.h:25,
                 from ../nptl/descr.h:32,
                 from ../sysdeps/aarch64/nptl/tls.h:44,
                 from ../include/errno.h:25,
                 from ../sysdeps/unix/sysv/linux/sysdep.h:23,
                 from ../sysdeps/unix/sysv/linux/generic/sysdep.h:22,
                 from ../sysdeps/unix/sysv/linux/aarch64/sysdep.h:24,
                 from <stdin>:1:
../sysdeps/nptl/pthread.h:734:47: error: argument 1 of type ‘struct
__jmp_buf_tag *’ declared as a pointer [-Werror=array-parameter=]
  734 | extern int __sigsetjmp (struct __jmp_buf_tag *__env, int __savemask)
__THROWNL;
      |                         ~~~~~~~~~~~~~~~~~~~~~~^~~~~
In file included from ../include/setjmp.h:2,
                 from ../nptl/descr.h:24,
                 from ../sysdeps/aarch64/nptl/tls.h:44,
                 from ../include/errno.h:25,
                 from ../sysdeps/unix/sysv/linux/sysdep.h:23,
                 from ../sysdeps/unix/sysv/linux/generic/sysdep.h:22,
                 from ../sysdeps/unix/sysv/linux/aarch64/sysdep.h:24,
                 from <stdin>:1:
../setjmp/setjmp.h:54:46: note: previously declared as an array ‘struct
__jmp_buf_tag[1]’
   54 | extern int __sigsetjmp (struct __jmp_buf_tag __env[1], int __savemask)
__THROWNL;
      |                         ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~
cc1: all warnings being treated as errors


The build/host/target setup is:
Build: x86_64-linux-gnu (Ubuntu 18.04)
Host: x86_64-linux-gnu
Target: aarch64-none-linux-gnu, aarch64_be-none-linux-gnu,
arm-none-linux-gnueabi, arm-none-linux-gnueabihf


This was mentioned in
https://gcc.gnu.org/pipermail/gcc-patches/2020-September/554415.html and it
seems like the warning might need to be suppressed in glibc.

[1]
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=6450f07388f9fe575a489c9309c36012b17b88b0

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-09-22 13:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22 13:07 vvinayag at arm dot com [this message]
2020-09-22 13:08 ` [Bug build/26647] " vvinayag at arm dot com
2020-09-23 14:50 ` msc at linux dot ibm.com
2020-09-23 15:05 ` schwab@linux-m68k.org
2020-10-05 16:47 ` cvs-commit at gcc dot gnu.org
2020-10-06 11:43 ` schwab@linux-m68k.org
2020-10-18 20:01 ` schwab@linux-m68k.org
2020-10-25 22:22 ` schwab@linux-m68k.org
2020-10-30 21:38 ` cvs-commit at gcc dot gnu.org
2020-10-30 21:44 ` jsm28 at gcc dot gnu.org
2021-09-07 11:07 ` bonzini at gnu dot org

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=bug-26647-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).