public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anders at kaseorg dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/39985] New: Type qualifiers not actually ignored on function return type Date: Thu, 30 Apr 2009 23:45:00 -0000 [thread overview] Message-ID: <bug-39985-7274@http.gcc.gnu.org/bugzilla/> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1179 bytes --] The warning printed with -Wignored-qualifiers (warning: type qualifiers ignored on function return type) seems to be lying. The const on a functions return type is not actually ignored, as can be demonstrated using typeof(). I think that the warning should be right and the typeof() behavior is wrong, but Im not actually sure. int f(void); const int g(void); /* warning: type qualifiers ignored on function return type */ typeof(f()) a; a = 5; typeof(g()) b; b = 5; /* error: assignment of read-only variable b */ Another thing that seems similarly strange is that a statement expression can return a const type, even though it is not an lvalue: const int x = 5; typeof( ({ x; }) ) y; y = 5; /* error: assignment of read-only variable y */ -- Summary: Type qualifiers not actually ignored on function return type Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: anders at kaseorg dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39985
next reply other threads:[~2009-04-30 23:45 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-30 23:45 anders at kaseorg dot com [this message] 2009-11-21 12:24 ` [Bug c/39985] " gcc at magfr dot user dot lysator dot liu dot se 2009-11-22 20:24 ` jsm28 at gcc dot gnu dot org 2009-11-27 7:33 ` anders at kaseorg dot com
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-39985-7274@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).