From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-il1-x133.google.com (mail-il1-x133.google.com [IPv6:2607:f8b0:4864:20::133]) by sourceware.org (Postfix) with ESMTPS id 985E63858D37 for ; Tue, 30 Jun 2020 02:32:55 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 985E63858D37 Received: by mail-il1-x133.google.com with SMTP id a11so8086764ilk.0 for ; Mon, 29 Jun 2020 19:32:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Z45RtgIyK6YDobiAaG7rM4RPu+qrFHTrHz277chK46E=; b=iAHJQLqnvTpU5nNzmKH8IkTHz026LNxbuELMFZrjByUyJtkl79jFvwHFvh8gb8Mhsw 5sRt6jL673JINqh7YxnKWc6gUbIoSFJhD4lVOpSiw50kfrALKoYu37RFSfZmvculxrHX lmduQMOBp2vcL4W7pZ0XUlETVYBjAbEuj6vPgByKUkQGinAXWts9p3HCYNoPQoFvjnxD l+VAfzCOw7quZtzWm0vp7J122F689ZXmh6qEmopVcTGUabl8iBzhHs+kZ+lvshpVA1xd LVszWWtoVSP8iu73KySnRPyKMF0Y5atc4zdOlh1ROnCDM/TWLqvNysY+IwTmNSxvE7MT Hgtg== X-Gm-Message-State: AOAM531xi50uT177Dlg+ULcNANVLuH/q60g4BwYmaSMkg0bT0xg4uAsA QPNIy8j9235iBWHAErlayIAghmN5L/Nls1F5YBKNU07OkhvE7Q== X-Google-Smtp-Source: ABdhPJy6Y3bnBqmgNvkH2wIA61AlXzGeqNMRl3vAY6rXd2wgKW7CEMmNw87jMeuZMbDu6DVyRjPpR291T3glWvrzIoc= X-Received: by 2002:a92:bb91:: with SMTP id x17mr493909ilk.156.1593484374701; Mon, 29 Jun 2020 19:32:54 -0700 (PDT) MIME-Version: 1.0 From: Haoxin Tu Date: Tue, 30 Jun 2020 10:32:18 +0800 Message-ID: Subject: How GCC treats ice-on-invalid-code? To: gcc-bugs@gcc.gnu.org X-Spam-Status: No, score=-3.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, KAM_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2020 02:32:57 -0000 Hi, there, Our team just develop a c++ code generator tool to testing the compiler, and those days I have reported 13 ICE bugs in ice-on-invalid-bugs. Here are the bugs links: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95972 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95956 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95955 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95954 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95925 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95930 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95931 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95927 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95932 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95935 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95945 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95938 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95937 Until now, only the last two cases are confirmed. So I am wondering that how GCC treats with those cases in ice-on-invalid-code? I mean, our team is focusing on improving the quality of the mature productive compilers. If those bugs are useless for GCC, maybe I should stop reporting similar issues. Waiting for your reply. Thank you very much! Best regrades, Haoxin