2023-01-01 14:08:42 +08:00
|
|
|
/* Copyright (C) 2017-2023 Free Software Foundation, Inc.
|
2017-06-22 16:31:20 +08:00
|
|
|
|
|
|
|
|
This program is free software; you can redistribute it and/or modify
|
|
|
|
|
it under the terms of the GNU General Public License as published by
|
|
|
|
|
the Free Software Foundation; either version 3 of the License, or
|
|
|
|
|
(at your option) any later version.
|
|
|
|
|
|
|
|
|
|
This program is distributed in the hope that it will be useful,
|
|
|
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
|
GNU General Public License for more details.
|
|
|
|
|
|
|
|
|
|
You should have received a copy of the GNU General Public License
|
|
|
|
|
along with this program. If not, see <http://www.gnu.org/licenses/>. */
|
|
|
|
|
|
2018-06-02 00:38:22 +08:00
|
|
|
#ifndef DIAGNOSTICS_H
|
|
|
|
|
#define DIAGNOSTICS_H
|
2017-06-22 16:31:20 +08:00
|
|
|
|
2018-07-06 13:37:08 +08:00
|
|
|
/* If at all possible, fix the source rather than using these macros
|
|
|
|
|
to silence warnings. If you do use these macros be aware that
|
|
|
|
|
you'll need to condition their use on particular compiler versions,
|
|
|
|
|
which can be done for gcc using ansidecl.h's GCC_VERSION macro.
|
|
|
|
|
|
|
|
|
|
gcc versions between 4.2 and 4.6 do not allow pragma control of
|
|
|
|
|
diagnostics inside functions, giving a hard error if you try to use
|
|
|
|
|
the finer control available with later versions.
|
|
|
|
|
gcc prior to 4.2 warns about diagnostic push and pop.
|
|
|
|
|
|
|
|
|
|
The other macros have restrictions too, for example gcc-5, gcc-6
|
|
|
|
|
and gcc-7 warn that -Wstringop-truncation is unknown, unless you
|
|
|
|
|
also add DIAGNOSTIC_IGNORE ("-Wpragma"). */
|
|
|
|
|
|
2017-06-22 16:31:20 +08:00
|
|
|
#ifdef __GNUC__
|
|
|
|
|
# define DIAGNOSTIC_PUSH _Pragma ("GCC diagnostic push")
|
|
|
|
|
# define DIAGNOSTIC_POP _Pragma ("GCC diagnostic pop")
|
2018-06-04 21:33:07 +08:00
|
|
|
|
|
|
|
|
/* Stringification. */
|
|
|
|
|
# define DIAGNOSTIC_STRINGIFY_1(x) #x
|
|
|
|
|
# define DIAGNOSTIC_STRINGIFY(x) DIAGNOSTIC_STRINGIFY_1 (x)
|
|
|
|
|
|
2017-06-22 16:31:20 +08:00
|
|
|
# define DIAGNOSTIC_IGNORE(option) \
|
2018-06-04 21:33:07 +08:00
|
|
|
_Pragma (DIAGNOSTIC_STRINGIFY (GCC diagnostic ignored option))
|
gdb, include: replace pragmas with DIAGNOSTIC macros, fix build with g++ 4.8
When introducing this code, I forgot that we had some macros for this.
Replace some "manual" pragma diagnostic with some DIAGNOSTIC_* macros,
provided by include/diagnostics.h.
In diagnostics.h:
- Add DIAGNOSTIC_ERROR, to enable a diagnostic at error level.
- Add DIAGNOSTIC_ERROR_SWITCH, to enable -Wswitch at error level, for
both gcc and clang.
Additionally, using DIAGNOSTIC_PUSH, DIAGNOSTIC_ERROR_SWITCH and
DIAGNOSTIC_POP seems to misbehave with g++ 4.8, where we see these
errors:
CXX ada-tasks.o
/home/smarchi/src/binutils-gdb/gdb/ada-tasks.c: In function void read_known_tasks():
/home/smarchi/src/binutils-gdb/gdb/ada-tasks.c:998:10: error: enumeration value ADA_TASKS_UNKNOWN not handled in switch [-Werror=switch]
switch (data->known_tasks_kind)
^
Because of the POP, the diagnostic should go back to being disabled,
since it was disabled in the beginning, but that's not what we see
here. Versions of GCC >= 5 compile correctly.
Work around this by making DIAGNOSTIC_ERROR_SWITCH a no-op for GCC < 5.
Note that this code (already as it exists in master today) enables
-Wswitch at the error level even if --disable-werror is passed. It
shouldn't be a problem, as it's not like a new enumerator will appear
out of nowhere and cause a build error if building with future
compilers. Still, for correctness, we would ideally want to ask the
compiler to enable -Wswitch at its default level (as if the user had
passed -Wswitch on the command-line). There doesn't seem to be a way to
do this.
Change-Id: Id33ebec3de39bd449409ea0bab59831289ffe82d
2021-12-02 21:23:12 +08:00
|
|
|
# define DIAGNOSTIC_ERROR(option) \
|
|
|
|
|
_Pragma (DIAGNOSTIC_STRINGIFY (GCC diagnostic error option))
|
2017-06-22 16:31:20 +08:00
|
|
|
#else
|
|
|
|
|
# define DIAGNOSTIC_PUSH
|
|
|
|
|
# define DIAGNOSTIC_POP
|
|
|
|
|
# define DIAGNOSTIC_IGNORE(option)
|
|
|
|
|
#endif
|
|
|
|
|
|
vec: Silence -Wunused-function warnings on clang
clang has a too aggressive (or broken, depends on how you want to see
it) -Wunused-function warning, which is triggered by the functions
defined by DEF_VEC_* but not used in the current source file. Normally,
it won't warn about unused static inline functions defined in header
files, because it's expected that a source file won't use all functions
defined in a header file it includes. However, if the DEF_VEC_* macro
is used in a source file, it considers those functions as defined in the
source file, which leads it to think that we should remove those
functions. It is therefore missing a check to see whether those
functions are resulting from macro expansion. A bug already exists for
that:
https://bugs.llvm.org//show_bug.cgi?id=22712
It's quite easy to silence this warning in a localized way, that is in
the DEF_VEC_* macros.
gdb/ChangeLog:
* common/diagnostics.h: Define macros for GCC.
(DIAGNOSTIC_IGNORE_UNUSED_FUNCTION): New macro.
* common/vec.h: Include diagnostics.h.
(DIAGNOSTIC_IGNORE_UNUSED_VEC_FUNCTION): New macro.
(DEF_VEC_I, DEF_VEC_P, DEF_VEC_O): Ignore -Wunused-function
warning.
2017-06-26 21:08:35 +08:00
|
|
|
#if defined (__clang__) /* clang */
|
|
|
|
|
|
2017-06-22 16:31:20 +08:00
|
|
|
# define DIAGNOSTIC_IGNORE_SELF_MOVE DIAGNOSTIC_IGNORE ("-Wself-move")
|
2018-07-06 09:50:12 +08:00
|
|
|
# define DIAGNOSTIC_IGNORE_DEPRECATED_DECLARATIONS \
|
|
|
|
|
DIAGNOSTIC_IGNORE ("-Wdeprecated-declarations")
|
2017-06-26 21:08:35 +08:00
|
|
|
# define DIAGNOSTIC_IGNORE_DEPRECATED_REGISTER \
|
|
|
|
|
DIAGNOSTIC_IGNORE ("-Wdeprecated-register")
|
2017-12-31 12:33:26 +08:00
|
|
|
# if __has_warning ("-Wenum-compare-switch")
|
|
|
|
|
# define DIAGNOSTIC_IGNORE_SWITCH_DIFFERENT_ENUM_TYPES \
|
|
|
|
|
DIAGNOSTIC_IGNORE ("-Wenum-compare-switch")
|
|
|
|
|
# endif
|
2018-09-06 11:21:51 +08:00
|
|
|
|
|
|
|
|
# define DIAGNOSTIC_IGNORE_FORMAT_NONLITERAL \
|
|
|
|
|
DIAGNOSTIC_IGNORE ("-Wformat-nonliteral")
|
|
|
|
|
|
2022-09-12 15:07:49 +08:00
|
|
|
# if __has_warning ("-Wuser-defined-warnings")
|
|
|
|
|
# define DIAGNOSTIC_IGNORE_USER_DEFINED_WARNINGS \
|
|
|
|
|
DIAGNOSTIC_IGNORE ("-Wuser-defined-warnings")
|
|
|
|
|
# endif
|
|
|
|
|
|
2022-09-12 16:04:40 +08:00
|
|
|
# if __has_warning ("-Wunused-but-set-variable")
|
|
|
|
|
# define DIAGNOSTIC_IGNORE_UNUSED_BUT_SET_VARIABLE \
|
|
|
|
|
DIAGNOSTIC_IGNORE ("-Wunused-but-set-variable")
|
|
|
|
|
# endif
|
|
|
|
|
|
gdb, include: replace pragmas with DIAGNOSTIC macros, fix build with g++ 4.8
When introducing this code, I forgot that we had some macros for this.
Replace some "manual" pragma diagnostic with some DIAGNOSTIC_* macros,
provided by include/diagnostics.h.
In diagnostics.h:
- Add DIAGNOSTIC_ERROR, to enable a diagnostic at error level.
- Add DIAGNOSTIC_ERROR_SWITCH, to enable -Wswitch at error level, for
both gcc and clang.
Additionally, using DIAGNOSTIC_PUSH, DIAGNOSTIC_ERROR_SWITCH and
DIAGNOSTIC_POP seems to misbehave with g++ 4.8, where we see these
errors:
CXX ada-tasks.o
/home/smarchi/src/binutils-gdb/gdb/ada-tasks.c: In function void read_known_tasks():
/home/smarchi/src/binutils-gdb/gdb/ada-tasks.c:998:10: error: enumeration value ADA_TASKS_UNKNOWN not handled in switch [-Werror=switch]
switch (data->known_tasks_kind)
^
Because of the POP, the diagnostic should go back to being disabled,
since it was disabled in the beginning, but that's not what we see
here. Versions of GCC >= 5 compile correctly.
Work around this by making DIAGNOSTIC_ERROR_SWITCH a no-op for GCC < 5.
Note that this code (already as it exists in master today) enables
-Wswitch at the error level even if --disable-werror is passed. It
shouldn't be a problem, as it's not like a new enumerator will appear
out of nowhere and cause a build error if building with future
compilers. Still, for correctness, we would ideally want to ask the
compiler to enable -Wswitch at its default level (as if the user had
passed -Wswitch on the command-line). There doesn't seem to be a way to
do this.
Change-Id: Id33ebec3de39bd449409ea0bab59831289ffe82d
2021-12-02 21:23:12 +08:00
|
|
|
# define DIAGNOSTIC_ERROR_SWITCH \
|
|
|
|
|
DIAGNOSTIC_ERROR ("-Wswitch")
|
|
|
|
|
|
gdbsupport: ignore -Wenum-constexpr-conversion in enum-flags.h
When building with clang 16, we get:
CXX gdb.o
In file included from /home/smarchi/src/binutils-gdb/gdb/gdb.c:19:
In file included from /home/smarchi/src/binutils-gdb/gdb/defs.h:65:
/home/smarchi/src/binutils-gdb/gdb/../gdbsupport/enum-flags.h:95:52: error: integer value -1 is outside the valid range of values [0, 15] for this enumeration type [-Wenum-constexpr-conversion]
integer_for_size<sizeof (T), static_cast<bool>(T (-1) < T (0))>::type
^
The error message does not make it clear in the context of which enum
flag this fails (i.e. what is T in this context), but it doesn't really
matter, we have similar warning/errors for many of them, if we let the
build go through.
clang is right that the value -1 is invalid for the enum type we cast -1
to. However, we do need this expression in order to select an integer
type with the appropriate signedness. That is, with the same signedness
as the underlying type of the enum.
I first wondered if that was really needed, if we couldn't use
std::underlying_type for that. It turns out that the comment just above
says:
/* Note that std::underlying_type<enum_type> is not what we want here,
since that returns unsigned int even when the enum decays to signed
int. */
I was surprised, because std::is_signed<std::underlying_type<enum_type>>
returns the right thing. So I tried replacing all this with
std::underlying_type, see if that would work. Doing so causes some
build failures in unittests/enum-flags-selftests.c:
CXX unittests/enum-flags-selftests.o
/home/smarchi/src/binutils-gdb/gdb/unittests/enum-flags-selftests.c:254:1: error: static assertion failed due to requirement 'gdb::is_same<selftests::enum_flags_tests::check_valid_expr254::archetype<enum_flags<s
elftests::enum_flags_tests::RE>, selftests::enum_flags_tests::RE, enum_flags<selftests::enum_flags_tests::RE2>, selftests::enum_flags_tests::RE2, enum_flags<selftests::enum_flags_tests::URE>, selftests::enum_fla
gs_tests::URE, int>, selftests::enum_flags_tests::check_valid_expr254::archetype<enum_flags<selftests::enum_flags_tests::RE>, selftests::enum_flags_tests::RE, enum_flags<selftests::enum_flags_tests::RE2>, selfte
sts::enum_flags_tests::RE2, enum_flags<selftests::enum_flags_tests::URE>, selftests::enum_flags_tests::URE, unsigned int>>::value == true':
CHECK_VALID (true, int, true ? EF () : EF2 ())
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/smarchi/src/binutils-gdb/gdb/unittests/enum-flags-selftests.c:91:3: note: expanded from macro 'CHECK_VALID'
CHECK_VALID_EXPR_6 (EF, RE, EF2, RE2, UEF, URE, VALID, EXPR_TYPE, EXPR)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/smarchi/src/binutils-gdb/gdb/../gdbsupport/valid-expr.h:105:3: note: expanded from macro 'CHECK_VALID_EXPR_6'
CHECK_VALID_EXPR_INT (ESC_PARENS (typename T1, typename T2, \
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/smarchi/src/binutils-gdb/gdb/../gdbsupport/valid-expr.h:66:3: note: expanded from macro 'CHECK_VALID_EXPR_INT'
static_assert (gdb::is_detected_exact<archetype<TYPES, EXPR_TYPE>, \
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This is a bit hard to decode, but basically enumerations have the
following funny property that they decay into a signed int, even if
their implicit underlying type is unsigned. This code:
enum A {};
enum B {};
int main() {
std::cout << std::is_signed<std::underlying_type<A>::type>::value
<< std::endl;
std::cout << std::is_signed<std::underlying_type<B>::type>::value
<< std::endl;
auto result = true ? A() : B();
std::cout << std::is_signed<decltype(result)>::value << std::endl;
}
produces:
0
0
1
So, the "CHECK_VALID" above checks that this property works for enum flags the
same way as it would if you were using their underlying enum types. And
somehow, changing integer_for_size to use std::underlying_type breaks that.
Since the current code does what we want, and I don't see any way of doing it
differently, ignore -Wenum-constexpr-conversion around it.
Change-Id: Ibc82ae7bbdb812102ae3f1dd099fc859dc6f3cc2
2023-02-24 01:35:40 +08:00
|
|
|
# if __has_warning ("-Wenum-constexpr-conversion")
|
|
|
|
|
# define DIAGNOSTIC_IGNORE_ENUM_CONSTEXPR_CONVERSION \
|
|
|
|
|
DIAGNOSTIC_IGNORE ("-Wenum-constexpr-conversion")
|
|
|
|
|
# endif
|
|
|
|
|
|
vec: Silence -Wunused-function warnings on clang
clang has a too aggressive (or broken, depends on how you want to see
it) -Wunused-function warning, which is triggered by the functions
defined by DEF_VEC_* but not used in the current source file. Normally,
it won't warn about unused static inline functions defined in header
files, because it's expected that a source file won't use all functions
defined in a header file it includes. However, if the DEF_VEC_* macro
is used in a source file, it considers those functions as defined in the
source file, which leads it to think that we should remove those
functions. It is therefore missing a check to see whether those
functions are resulting from macro expansion. A bug already exists for
that:
https://bugs.llvm.org//show_bug.cgi?id=22712
It's quite easy to silence this warning in a localized way, that is in
the DEF_VEC_* macros.
gdb/ChangeLog:
* common/diagnostics.h: Define macros for GCC.
(DIAGNOSTIC_IGNORE_UNUSED_FUNCTION): New macro.
* common/vec.h: Include diagnostics.h.
(DIAGNOSTIC_IGNORE_UNUSED_VEC_FUNCTION): New macro.
(DEF_VEC_I, DEF_VEC_P, DEF_VEC_O): Ignore -Wunused-function
warning.
2017-06-26 21:08:35 +08:00
|
|
|
#elif defined (__GNUC__) /* GCC */
|
|
|
|
|
|
2022-10-27 12:33:37 +08:00
|
|
|
# define DIAGNOSTIC_IGNORE_DEPRECATED_DECLARATIONS \
|
|
|
|
|
DIAGNOSTIC_IGNORE ("-Wdeprecated-declarations")
|
|
|
|
|
|
2020-08-22 06:20:55 +08:00
|
|
|
# if __GNUC__ >= 7
|
|
|
|
|
# define DIAGNOSTIC_IGNORE_DEPRECATED_REGISTER \
|
|
|
|
|
DIAGNOSTIC_IGNORE ("-Wregister")
|
|
|
|
|
# endif
|
|
|
|
|
|
2018-06-05 01:01:34 +08:00
|
|
|
# define DIAGNOSTIC_IGNORE_STRINGOP_TRUNCATION \
|
2018-06-04 21:33:07 +08:00
|
|
|
DIAGNOSTIC_IGNORE ("-Wstringop-truncation")
|
2018-09-06 11:21:51 +08:00
|
|
|
|
2022-06-15 15:03:03 +08:00
|
|
|
# if __GNUC__ >= 11
|
2022-05-04 07:17:31 +08:00
|
|
|
# define DIAGNOSTIC_IGNORE_STRINGOP_OVERREAD \
|
|
|
|
|
DIAGNOSTIC_IGNORE ("-Wstringop-overread")
|
2022-06-15 15:03:03 +08:00
|
|
|
#endif
|
2022-05-04 07:17:31 +08:00
|
|
|
|
2018-09-06 11:21:51 +08:00
|
|
|
# define DIAGNOSTIC_IGNORE_FORMAT_NONLITERAL \
|
|
|
|
|
DIAGNOSTIC_IGNORE ("-Wformat-nonliteral")
|
|
|
|
|
|
2022-09-12 16:04:40 +08:00
|
|
|
# if __GNUC__ >= 5
|
|
|
|
|
# define DIAGNOSTIC_IGNORE_UNUSED_BUT_SET_VARIABLE \
|
|
|
|
|
DIAGNOSTIC_IGNORE ("-Wunused-but-set-variable")
|
|
|
|
|
# endif
|
|
|
|
|
|
2022-10-03 22:56:24 +08:00
|
|
|
# if __GNUC__ >= 13
|
|
|
|
|
# define DIAGNOSTIC_IGNORE_SELF_MOVE DIAGNOSTIC_IGNORE ("-Wself-move")
|
|
|
|
|
# endif
|
|
|
|
|
|
gdb, include: replace pragmas with DIAGNOSTIC macros, fix build with g++ 4.8
When introducing this code, I forgot that we had some macros for this.
Replace some "manual" pragma diagnostic with some DIAGNOSTIC_* macros,
provided by include/diagnostics.h.
In diagnostics.h:
- Add DIAGNOSTIC_ERROR, to enable a diagnostic at error level.
- Add DIAGNOSTIC_ERROR_SWITCH, to enable -Wswitch at error level, for
both gcc and clang.
Additionally, using DIAGNOSTIC_PUSH, DIAGNOSTIC_ERROR_SWITCH and
DIAGNOSTIC_POP seems to misbehave with g++ 4.8, where we see these
errors:
CXX ada-tasks.o
/home/smarchi/src/binutils-gdb/gdb/ada-tasks.c: In function void read_known_tasks():
/home/smarchi/src/binutils-gdb/gdb/ada-tasks.c:998:10: error: enumeration value ADA_TASKS_UNKNOWN not handled in switch [-Werror=switch]
switch (data->known_tasks_kind)
^
Because of the POP, the diagnostic should go back to being disabled,
since it was disabled in the beginning, but that's not what we see
here. Versions of GCC >= 5 compile correctly.
Work around this by making DIAGNOSTIC_ERROR_SWITCH a no-op for GCC < 5.
Note that this code (already as it exists in master today) enables
-Wswitch at the error level even if --disable-werror is passed. It
shouldn't be a problem, as it's not like a new enumerator will appear
out of nowhere and cause a build error if building with future
compilers. Still, for correctness, we would ideally want to ask the
compiler to enable -Wswitch at its default level (as if the user had
passed -Wswitch on the command-line). There doesn't seem to be a way to
do this.
Change-Id: Id33ebec3de39bd449409ea0bab59831289ffe82d
2021-12-02 21:23:12 +08:00
|
|
|
/* GCC 4.8's "diagnostic push/pop" seems broken when using this, -Wswitch
|
|
|
|
|
remains enabled at the error level even after a pop. Therefore, don't
|
|
|
|
|
use it for GCC < 5. */
|
|
|
|
|
# if __GNUC__ >= 5
|
|
|
|
|
# define DIAGNOSTIC_ERROR_SWITCH DIAGNOSTIC_ERROR ("-Wswitch")
|
|
|
|
|
# endif
|
|
|
|
|
|
2018-06-04 21:33:07 +08:00
|
|
|
#endif
|
vec: Silence -Wunused-function warnings on clang
clang has a too aggressive (or broken, depends on how you want to see
it) -Wunused-function warning, which is triggered by the functions
defined by DEF_VEC_* but not used in the current source file. Normally,
it won't warn about unused static inline functions defined in header
files, because it's expected that a source file won't use all functions
defined in a header file it includes. However, if the DEF_VEC_* macro
is used in a source file, it considers those functions as defined in the
source file, which leads it to think that we should remove those
functions. It is therefore missing a check to see whether those
functions are resulting from macro expansion. A bug already exists for
that:
https://bugs.llvm.org//show_bug.cgi?id=22712
It's quite easy to silence this warning in a localized way, that is in
the DEF_VEC_* macros.
gdb/ChangeLog:
* common/diagnostics.h: Define macros for GCC.
(DIAGNOSTIC_IGNORE_UNUSED_FUNCTION): New macro.
* common/vec.h: Include diagnostics.h.
(DIAGNOSTIC_IGNORE_UNUSED_VEC_FUNCTION): New macro.
(DEF_VEC_I, DEF_VEC_P, DEF_VEC_O): Ignore -Wunused-function
warning.
2017-06-26 21:08:35 +08:00
|
|
|
|
2018-06-04 21:33:07 +08:00
|
|
|
#ifndef DIAGNOSTIC_IGNORE_SELF_MOVE
|
2017-06-22 16:31:20 +08:00
|
|
|
# define DIAGNOSTIC_IGNORE_SELF_MOVE
|
2018-06-04 21:33:07 +08:00
|
|
|
#endif
|
|
|
|
|
|
2018-07-06 09:50:12 +08:00
|
|
|
#ifndef DIAGNOSTIC_IGNORE_DEPRECATED_DECLARATIONS
|
|
|
|
|
# define DIAGNOSTIC_IGNORE_DEPRECATED_DECLARATIONS
|
|
|
|
|
#endif
|
|
|
|
|
|
2018-06-04 21:33:07 +08:00
|
|
|
#ifndef DIAGNOSTIC_IGNORE_DEPRECATED_REGISTER
|
2017-06-26 21:08:35 +08:00
|
|
|
# define DIAGNOSTIC_IGNORE_DEPRECATED_REGISTER
|
2018-06-04 21:33:07 +08:00
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#ifndef DIAGNOSTIC_IGNORE_SWITCH_DIFFERENT_ENUM_TYPES
|
2017-12-30 12:32:13 +08:00
|
|
|
# define DIAGNOSTIC_IGNORE_SWITCH_DIFFERENT_ENUM_TYPES
|
2018-06-04 21:33:07 +08:00
|
|
|
#endif
|
2017-12-30 12:32:13 +08:00
|
|
|
|
2018-06-04 21:33:07 +08:00
|
|
|
#ifndef DIAGNOSTIC_IGNORE_STRINGOP_TRUNCATION
|
|
|
|
|
# define DIAGNOSTIC_IGNORE_STRINGOP_TRUNCATION
|
2017-06-22 16:31:20 +08:00
|
|
|
#endif
|
|
|
|
|
|
2022-05-04 07:17:31 +08:00
|
|
|
#ifndef DIAGNOSTIC_IGNORE_STRINGOP_OVERREAD
|
|
|
|
|
# define DIAGNOSTIC_IGNORE_STRINGOP_OVERREAD
|
|
|
|
|
#endif
|
|
|
|
|
|
2018-09-06 11:21:51 +08:00
|
|
|
#ifndef DIAGNOSTIC_IGNORE_FORMAT_NONLITERAL
|
|
|
|
|
# define DIAGNOSTIC_IGNORE_FORMAT_NONLITERAL
|
|
|
|
|
#endif
|
|
|
|
|
|
2022-09-12 15:07:49 +08:00
|
|
|
#ifndef DIAGNOSTIC_IGNORE_USER_DEFINED_WARNINGS
|
|
|
|
|
# define DIAGNOSTIC_IGNORE_USER_DEFINED_WARNINGS
|
|
|
|
|
#endif
|
|
|
|
|
|
2022-09-12 16:04:40 +08:00
|
|
|
#ifndef DIAGNOSTIC_IGNORE_UNUSED_BUT_SET_VARIABLE
|
|
|
|
|
# define DIAGNOSTIC_IGNORE_UNUSED_BUT_SET_VARIABLE
|
|
|
|
|
#endif
|
|
|
|
|
|
gdb, include: replace pragmas with DIAGNOSTIC macros, fix build with g++ 4.8
When introducing this code, I forgot that we had some macros for this.
Replace some "manual" pragma diagnostic with some DIAGNOSTIC_* macros,
provided by include/diagnostics.h.
In diagnostics.h:
- Add DIAGNOSTIC_ERROR, to enable a diagnostic at error level.
- Add DIAGNOSTIC_ERROR_SWITCH, to enable -Wswitch at error level, for
both gcc and clang.
Additionally, using DIAGNOSTIC_PUSH, DIAGNOSTIC_ERROR_SWITCH and
DIAGNOSTIC_POP seems to misbehave with g++ 4.8, where we see these
errors:
CXX ada-tasks.o
/home/smarchi/src/binutils-gdb/gdb/ada-tasks.c: In function void read_known_tasks():
/home/smarchi/src/binutils-gdb/gdb/ada-tasks.c:998:10: error: enumeration value ADA_TASKS_UNKNOWN not handled in switch [-Werror=switch]
switch (data->known_tasks_kind)
^
Because of the POP, the diagnostic should go back to being disabled,
since it was disabled in the beginning, but that's not what we see
here. Versions of GCC >= 5 compile correctly.
Work around this by making DIAGNOSTIC_ERROR_SWITCH a no-op for GCC < 5.
Note that this code (already as it exists in master today) enables
-Wswitch at the error level even if --disable-werror is passed. It
shouldn't be a problem, as it's not like a new enumerator will appear
out of nowhere and cause a build error if building with future
compilers. Still, for correctness, we would ideally want to ask the
compiler to enable -Wswitch at its default level (as if the user had
passed -Wswitch on the command-line). There doesn't seem to be a way to
do this.
Change-Id: Id33ebec3de39bd449409ea0bab59831289ffe82d
2021-12-02 21:23:12 +08:00
|
|
|
#ifndef DIAGNOSTIC_ERROR_SWITCH
|
|
|
|
|
# define DIAGNOSTIC_ERROR_SWITCH
|
|
|
|
|
#endif
|
|
|
|
|
|
gdbsupport: ignore -Wenum-constexpr-conversion in enum-flags.h
When building with clang 16, we get:
CXX gdb.o
In file included from /home/smarchi/src/binutils-gdb/gdb/gdb.c:19:
In file included from /home/smarchi/src/binutils-gdb/gdb/defs.h:65:
/home/smarchi/src/binutils-gdb/gdb/../gdbsupport/enum-flags.h:95:52: error: integer value -1 is outside the valid range of values [0, 15] for this enumeration type [-Wenum-constexpr-conversion]
integer_for_size<sizeof (T), static_cast<bool>(T (-1) < T (0))>::type
^
The error message does not make it clear in the context of which enum
flag this fails (i.e. what is T in this context), but it doesn't really
matter, we have similar warning/errors for many of them, if we let the
build go through.
clang is right that the value -1 is invalid for the enum type we cast -1
to. However, we do need this expression in order to select an integer
type with the appropriate signedness. That is, with the same signedness
as the underlying type of the enum.
I first wondered if that was really needed, if we couldn't use
std::underlying_type for that. It turns out that the comment just above
says:
/* Note that std::underlying_type<enum_type> is not what we want here,
since that returns unsigned int even when the enum decays to signed
int. */
I was surprised, because std::is_signed<std::underlying_type<enum_type>>
returns the right thing. So I tried replacing all this with
std::underlying_type, see if that would work. Doing so causes some
build failures in unittests/enum-flags-selftests.c:
CXX unittests/enum-flags-selftests.o
/home/smarchi/src/binutils-gdb/gdb/unittests/enum-flags-selftests.c:254:1: error: static assertion failed due to requirement 'gdb::is_same<selftests::enum_flags_tests::check_valid_expr254::archetype<enum_flags<s
elftests::enum_flags_tests::RE>, selftests::enum_flags_tests::RE, enum_flags<selftests::enum_flags_tests::RE2>, selftests::enum_flags_tests::RE2, enum_flags<selftests::enum_flags_tests::URE>, selftests::enum_fla
gs_tests::URE, int>, selftests::enum_flags_tests::check_valid_expr254::archetype<enum_flags<selftests::enum_flags_tests::RE>, selftests::enum_flags_tests::RE, enum_flags<selftests::enum_flags_tests::RE2>, selfte
sts::enum_flags_tests::RE2, enum_flags<selftests::enum_flags_tests::URE>, selftests::enum_flags_tests::URE, unsigned int>>::value == true':
CHECK_VALID (true, int, true ? EF () : EF2 ())
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/smarchi/src/binutils-gdb/gdb/unittests/enum-flags-selftests.c:91:3: note: expanded from macro 'CHECK_VALID'
CHECK_VALID_EXPR_6 (EF, RE, EF2, RE2, UEF, URE, VALID, EXPR_TYPE, EXPR)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/smarchi/src/binutils-gdb/gdb/../gdbsupport/valid-expr.h:105:3: note: expanded from macro 'CHECK_VALID_EXPR_6'
CHECK_VALID_EXPR_INT (ESC_PARENS (typename T1, typename T2, \
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/smarchi/src/binutils-gdb/gdb/../gdbsupport/valid-expr.h:66:3: note: expanded from macro 'CHECK_VALID_EXPR_INT'
static_assert (gdb::is_detected_exact<archetype<TYPES, EXPR_TYPE>, \
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This is a bit hard to decode, but basically enumerations have the
following funny property that they decay into a signed int, even if
their implicit underlying type is unsigned. This code:
enum A {};
enum B {};
int main() {
std::cout << std::is_signed<std::underlying_type<A>::type>::value
<< std::endl;
std::cout << std::is_signed<std::underlying_type<B>::type>::value
<< std::endl;
auto result = true ? A() : B();
std::cout << std::is_signed<decltype(result)>::value << std::endl;
}
produces:
0
0
1
So, the "CHECK_VALID" above checks that this property works for enum flags the
same way as it would if you were using their underlying enum types. And
somehow, changing integer_for_size to use std::underlying_type breaks that.
Since the current code does what we want, and I don't see any way of doing it
differently, ignore -Wenum-constexpr-conversion around it.
Change-Id: Ibc82ae7bbdb812102ae3f1dd099fc859dc6f3cc2
2023-02-24 01:35:40 +08:00
|
|
|
#ifndef DIAGNOSTIC_IGNORE_ENUM_CONSTEXPR_CONVERSION
|
|
|
|
|
# define DIAGNOSTIC_IGNORE_ENUM_CONSTEXPR_CONVERSION
|
|
|
|
|
#endif
|
|
|
|
|
|
2018-06-02 00:38:22 +08:00
|
|
|
#endif /* DIAGNOSTICS_H */
|
