Skip to content

Commit a70d80a

Browse files
Collect pending Changes entries for 2026-10-22 []
1 parent 992dedf commit a70d80a

3 files changed

Lines changed: 32 additions & 29 deletions

File tree

‎src/Changes‎

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,37 @@
11
Version 7.1
22

3+
10/22/26 [GH #305]
4+
Attribute namespaces that only start like a known one are not recognized
5+
6+
An attribute namespace was treated as known if it was merely the first part
7+
of the name of a known namespace; the whole name must now match.
8+
For example:
9+
10+
[[cl::x]] int a; // Warning: attribute namespace "cl" is unrecognized
11+
[[g::y]] int b; // Previously, the namespace was accepted.
12+
13+
14+
10/22/26 [GH #183]
15+
GNU compatibility: "inline" combined with "noinline" on a definition
16+
17+
In GNU and Clang C++ modes, the front end warned that a routine is both
18+
"inline" and "noinline" when a function definition was declared "inline" and
19+
had the GNU "noinline" attribute, but GCC accepts that combination silently
20+
(it is used, e.g., by Boost through "BOOST_NOINLINE inline"). For example:
21+
22+
inline __attribute__((noinline)) int f(int x) { // No warning now.
23+
return x;
24+
}
25+
26+
In C modes, where GCC and Clang warn about the combination in all of those
27+
cases, the behavior is unchanged.
28+
29+
Also, instantiating a function template (or a member function of a class
30+
template) that is both "inline" and "noinline" no longer repeats the warning
31+
"At end of source" for each instance, only the template declarations are
32+
checked.
33+
34+
335
10/21/26 [GH #335]
436
Type transformations of qualified function types
537

‎src/pending_changes/gh-183-inline-noinline.txt‎

Lines changed: 0 additions & 20 deletions
This file was deleted.

‎src/pending_changes/gh-305-attribute-namespace-exact-match.txt‎

Lines changed: 0 additions & 9 deletions
This file was deleted.

0 commit comments

Comments
 (0)