public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/103012] [11/12 Regression] ICE with #pragma GCC optimize followed by long line (4047 long) Date: Sun, 07 Nov 2021 03:11:34 +0000 [thread overview] Message-ID: <bug-103012-4-Mxaqr3ofKZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103012-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103012 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |11.3 Known to fail| |11.1.0 Keywords| |needs-bisection Summary|ICE with #pragma GCC |[11/12 Regression] ICE with |optimize followed by long |#pragma GCC optimize |line |followed by long line (4047 | |long) Known to work| |10.1.0, 7.5.0 --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- So decent testcase with macros, though you need -save-temps or preprocess it beforehand if you are invoking cc1plus directly. #pragma GCC optimize "Og" #define a1(a) a #define a2(a) a1(a)a1(a) #define a4(a) a2(a)a2(a) #define a8(a) a4(a)a4(a) #define a16(a) a8(a)a8(a) #define a32(a) a16(a)a16(a) #define a64(a) a32(a)a32(a) #define a128(a) a64(a)a64(a) #define a256(a) a128(a)a128(a) #define a512(a) a256(a)a256(a) #define a1024(a) a512(a)a512(a) #define a2048(a) a1024(a)a1024(a) a2048(a) ---------- CUT ------ What I found also is the line needs to be 4047 characters long. The above line will a little longer around 4096ish. Also this worked at r10-6101 but failed at r11-6338.
next prev parent reply other threads:[~2021-11-07 3:11 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-31 9:42 [Bug c++/103012] New: ICE with #pragma GCC optimize followed by long line pinskia at gcc dot gnu.org 2021-10-31 9:43 ` [Bug c++/103012] " pinskia at gcc dot gnu.org 2021-10-31 9:43 ` pinskia at gcc dot gnu.org 2021-11-01 9:42 ` marxin at gcc dot gnu.org 2021-11-01 9:52 ` marxin at gcc dot gnu.org 2021-11-07 3:11 ` pinskia at gcc dot gnu.org [this message] 2021-11-08 8:16 ` [Bug c++/103012] [11/12 Regression] ICE with #pragma GCC optimize followed by long line (4047 long) marxin at gcc dot gnu.org 2021-12-28 11:49 ` jakub at gcc dot gnu.org 2021-12-30 13:26 ` cvs-commit at gcc dot gnu.org 2021-12-30 13:39 ` [Bug c++/103012] [11 " jakub at gcc dot gnu.org 2022-01-24 9:20 ` cvs-commit at gcc dot gnu.org 2022-01-24 9:29 ` jakub at gcc dot gnu.org 2022-01-24 9:31 ` 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-103012-4-Mxaqr3ofKZ@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).