public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/93573] [8/9/10 Regression] internal compiler error: in force_constant_size, at gimplify.c:733 Date: Sat, 28 Mar 2020 09:31:13 +0000 [thread overview] Message-ID: <bug-93573-4-yRIhf6KAMN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-93573-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93573 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:c6a562de88c44a555e1688c212869b20b02151bc commit r10-7438-gc6a562de88c44a555e1688c212869b20b02151bc Author: Jakub Jelinek <jakub@redhat.com> Date: Sat Mar 28 10:30:31 2020 +0100 c: After issuing errors about array size, for error-recovery don't make the array VLA [PR93573] After we report various errors about array size, we set for error-recovery the size to be 1, but because size_int_const is false, it still means we pretend the array is a VLA, can emit a second diagnostics in that case etc. E.g. $ ./cc1.unpatched -quiet a.c a.c:1:5: error: size of array âfâ has non-integer type 1 | int f[100.0]; | ^ a.c:1:1: warning: variably modified âfâ at file scope 1 | int f[100.0]; | ^~~ $ ./cc1 -quiet a.c a.c:1:5: error: size of array âfâ has non-integer type 1 | int f[100.0]; | ^ 2020-03-28 Jakub Jelinek <jakub@redhat.com> PR c/93573 * c-decl.c (grokdeclarator): After issuing errors, set size_int_const to true after setting size to integer_one_node. * gcc.dg/pr93573-1.c: New test. * gcc.dg/pr93573-2.c: New test.
next prev parent reply other threads:[~2020-03-28 9:31 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-93573-4@http.gcc.gnu.org/bugzilla/> 2020-03-20 8:34 ` rguenth at gcc dot gnu.org 2020-03-27 16:40 ` jakub at gcc dot gnu.org 2020-03-27 18:02 ` jakub at gcc dot gnu.org 2020-03-27 18:04 ` jakub at gcc dot gnu.org 2020-03-28 9:31 ` cvs-commit at gcc dot gnu.org [this message] 2020-03-28 9:35 ` jakub at gcc dot gnu.org 2020-03-30 23:22 ` joseph at codesourcery dot com 2021-05-14 9:52 ` [Bug c/93573] [9/10/11/12 " jakub at gcc dot gnu.org 2021-06-01 8:16 ` rguenth at gcc dot gnu.org 2022-05-27 9:42 ` [Bug c/93573] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:39 ` jakub at gcc dot gnu.org 2023-07-07 10:36 ` [Bug c/93573] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-02-20 7:36 ` pinskia at gcc dot gnu.org 2024-02-20 7:43 ` jakub at gcc dot gnu.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-93573-4-yRIhf6KAMN@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).