public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/28289] New: composite_types called to do two different things Date: Thu, 06 Jul 2006 18:00:00 -0000 [thread overview] Message-ID: <bug-28289-5394@http.gcc.gnu.org/bugzilla/> (raw) composite_types is called in c-decl.c to merge function declarations, but in c-typeck.c to merge the types of two arms of a COND_EXPR. The former should result in a union of traits of the inputs, which composite_types computes, but the latter should give the intersection of traits unless the C standard says otherwise. In particular, when TREE_READONLY is set for a function type, that means that this function has no side effect, i.e. it is pure. When a cond expression yields a function type, it is pure only if both functions are pure. When a call is made through a COND_EXPR which is improperly marked as yielding a pure function pointer, and the result is ignored, the actual function call is not emitted. Likewise, when we merge the type of a function with a noreturn attribute with the type of a function without that attribute, merging the types for a COND_EXPR should yield a function type without this attribute. -- Summary: composite_types called to do two different things Product: gcc Version: 4.2.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: amylaar at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28289
next reply other threads:[~2006-07-06 18:00 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-07-06 18:00 amylaar at gcc dot gnu dot org [this message] 2006-07-07 9:30 ` [Bug c/28289] " rguenth at gcc dot gnu dot org 2006-07-07 16:47 ` amylaar at gcc dot gnu dot org 2006-08-17 13:23 ` amylaar at gcc dot gnu dot org 2008-01-13 18:36 ` rguenth at gcc dot gnu dot org
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-28289-5394@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).