From: Sandra Loosemore <sandra@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: GCC switch to C11 causes many testsuite compiler diagnostics
Date: Sat, 25 Oct 2014 17:04:00 -0000 [thread overview]
Message-ID: <544BD7E6.1050602@codesourcery.com> (raw)
Comparing my latest nios2 test results (with Pedro's thread patch) with
those from a checkout a couple weeks old, I noticed I had some new
ERRORs due to apparent compilation failures. I tracked this down to the
recent change on GCC mainline (r216247) to make the default C dialect
GNU11, which enables -Wimplicit-int and -Wimplicit-function-declaration
by default. I started working on a patch to fix the offending
testcases, but realized that there are hundreds of them. :-(
So, before I invest a lot more time on this, is updating the GDB
testsuite to use a more modern C dialect the Right Thing To Do? I'm
also wondering if it's really necessary to support compilers that can't
handle function prototypes in the testsuite (not defining PROTOTYPES
seems to be the default, in fact).
-Sandra
next reply other threads:[~2014-10-25 17:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 17:04 Sandra Loosemore [this message]
2014-10-25 17:28 ` Mark Kettenis
2014-10-30 16:23 ` Andreas Arnez
2014-10-31 19:02 ` Doug Evans
2014-10-31 19:23 ` Mark Kettenis
2014-10-31 19:29 ` Doug Evans
2014-11-03 11:02 ` Andreas Arnez
2014-10-30 16:07 ` Andreas Arnez
2014-10-30 22:26 ` Stan Shebs
2014-10-30 22:37 ` Sergio Durigan Junior
2014-11-23 7:27 ` Joel Brobecker
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=544BD7E6.1050602@codesourcery.com \
--to=sandra@codesourcery.com \
--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