public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simon.marchi at polymtl dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/31417] New: sim: -Wstrict-prototypes not enabled due to bad configure check
Date: Mon, 26 Feb 2024 14:54:01 +0000	[thread overview]
Message-ID: <bug-31417-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31417
           Summary: sim: -Wstrict-prototypes not enabled due to bad
                    configure check
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: sim
          Assignee: unassigned at sourceware dot org
          Reporter: simon.marchi at polymtl dot ca
                CC: vapier at gentoo dot org
  Target Milestone: ---

The sim directory attempts to enable the -Wstrict-prototypes compiler flag. 
While it is support in gcc, the flag is not enabled because the config check
results in:

configure:16654: ccache gcc -c -g3 -O0 -fsanitize=address -fmax-errors=1
-fdiagnostics-color=always     -Werror -Wstrict-prototypes  co
nftest.c >&5
conftest.c:163:1: error: function declaration isn't a prototype
[-Werror=strict-prototypes]
  163 | main ()
      | ^~~~

The main function in the config test is:

| int
| main ()
| {
| 
|   ;
|   return 0;
| }


So yeah, the flag is not enabled because it finds in the config test exactly
the kind of things it's meant to find :)

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

             reply	other threads:[~2024-02-26 14:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 14:54 simon.marchi at polymtl dot ca [this message]
2024-02-26 15:05 ` [Bug sim/31417] " simon.marchi at polymtl dot ca

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-31417-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).