public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rkl@connect.org.uk To: gcc-gnats@gcc.gnu.org Subject: c++/4093: Return type mis-match for (a?b:c) constructs in gcc/cp/cp-tree.h Date: Thu, 23 Aug 2001 07:16:00 -0000 [thread overview] Message-ID: <20010823141318.6275.qmail@sourceware.cygnus.com> (raw) >Number: 4093 >Category: c++ >Synopsis: Return type mis-match for (a?b:c) constructs in gcc/cp/cp-tree.h >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Aug 23 07:16:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: rkl@connect.org.uk >Release: unknown-1.0 >Organization: >Environment: HP-UX 11.00 (may apply to other platforms with "strict" ANSI C compilers) >Description: HP-UX's ANSI C compiler likes the conditional (a?b:c) construct to have matching types for the return values b and c (which is sensible, you'd agree :-) ). In gcc/cp/cp-tree.h, there is a mismatch in the #define's for SET_BINFO_MARKED(), CLEAR_BINFO_MARKED(), SET_BINFO_VTABLE_PATH_MARKED() and CLEAR_BINFO_VTABLE_PATH_MARKED() (lines 1668, 1669, 1674 and 1675). It turns out that the "true" part ("b" if you like) returns a (void), but the "false" part ("c") doesn't. >How-To-Repeat: Compile gcc 3.0.1 with a strict ANSI C compiler - I used the HP-UX 11.00 HP ANSI C compiler for this. >Fix: Cast the "else" part ("c") to a (void). For example: #define SET_BINFO_MARKED(NODE) (TREE_VIA_VIRTUAL(NODE)?SET_CLASSTYPE_MARKED(BINFO_TYPE(NODE)):(void)(TREE_LANG_FLAG_0(NODE)=1)) >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-08-23 7:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-08-23 7:16 rkl [this message] 2002-02-24 11:09 rodrigc
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=20010823141318.6275.qmail@sourceware.cygnus.com \ --to=rkl@connect.org.uk \ --cc=gcc-gnats@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).