public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/16631] [3.5 Regression] Problems inlining with enums Date: Tue, 20 Jul 2004 14:32:00 -0000 [thread overview] Message-ID: <20040720143228.12577.qmail@sourceware.org> (raw) In-Reply-To: <20040719172622.16631.roger@eyesopen.com> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-07-20 14:32 ------- Fixed by: * c-common.h (check_case_value): Remove prototype. (c_add_case_label): Adjust prototype. * c-common.c (check_case_value): Make static. (check_case_bounds): New function. (c_add_case_label): Use it. Take new argument orig_type. * c-typeck.c (struct c_switch): New orig_type field. (c_start_case): Set it. (do_case): Pass it to c_add_case_label. * expr.c (expand_expr_real_1): Don't warn for out-of-bounds cases from here. Add the labels in reverse order. * stmt.c (struct case_node): Adjust comment. Remove balance field. (add_case_node): Return nothing, don't check for duplicate cases. Insert new case nodes in a list, not in an AVL tree. (expand_end_case_type): Don't turn a case tree into a case list. (case_tree2list): Remove. * tree.h (add_case_node): Adjust prototype. cp/ * cp-tree.h (struct lang_decl_flags): Unify the template_info and thunk_alias, and the access and virtual_offset fields. (THUNK_VIRTUAL_OFFSET, THUNK_ALIAS): Adjust. * decl.c (finish_case_label): Update c_add_case_node call. testsuite/ * testsuite/gcc.dg/switch-warn-1.c: New test. * testsuite/gcc.dg/switch-warn-2.c: New test. * gcc.c-torture/compile/pr14730.c: Update -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16631
prev parent reply other threads:[~2004-07-20 14:32 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-19 17:26 [Bug middle-end/16631] New: " roger at eyesopen dot com 2004-07-19 17:32 ` [Bug middle-end/16631] " roger at eyesopen dot com 2004-07-19 17:37 ` pinskia at gcc dot gnu dot org 2004-07-19 17:44 ` roger at eyesopen dot com 2004-07-19 17:46 ` bangerth at dealii dot org 2004-07-19 18:03 ` bangerth at dealii dot org 2004-07-19 18:50 ` pinskia at gcc dot gnu dot org 2004-07-19 19:04 ` bangerth at dealii dot org 2004-07-19 20:09 ` roger at eyesopen dot com 2004-07-19 20:43 ` pinskia at gcc dot gnu dot org 2004-07-19 21:15 ` pinskia at gcc dot gnu dot org 2004-07-19 21:16 ` [Bug middle-end/16631] [3.5 Regression] " pinskia at gcc dot gnu dot org 2004-07-20 14:32 ` pinskia at gcc dot gnu dot org [this message]
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=20040720143228.12577.qmail@sourceware.org \ --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).