This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/68612] Const-compatibility in C
- From: "alexreg at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 03 Dec 2015 22:32:18 +0000
- Subject: [Bug c/68612] Const-compatibility in C
- Auto-submitted: auto-generated
- References: <bug-68612-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68612
--- Comment #6 from Alexander Regueiro <alexreg at gmail dot com> ---
Thatâs good to know. Do we have a suitable developer to take on this project? I
would do it myself, but Iâm not really qualified enough.
I suppose trunk wonât be in bug-fixing mode too longâ
> On 1 Dec 2015, at 23:35, joseph at codesourcery dot com <gcc-bugzilla@gcc.gnu.org> wrote:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68612
>
> --- Comment #5 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
> I'd consider this a reasonable extension (not suitable for adding while
> trunk is in bug-fixing mode, of course) for default (non-pedantic) mode,
> similar to the extension to use C++-like rules for arrays of qualified
> type. Similar to that, it requires a lot of care to make sure it doesn't
> cause valid code to be rejected, as well as thorough testcases.
>
> (To be clear, the C++ rule is not symmetric between const and other
> qualifiers; it allows adding arbitrary qualifiers in certain places if
> const is present at all levels of indirection beyond those where any
> qualifiers are added. For this purpose, in C, _Atomic should not be
> considered a qualifier, and you'd need to think about how address space
> qualifiers are involved.)
>
> --
> You are receiving this mail because:
> You reported the bug.