public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/60523] Warning flag for octal literals Date: Fri, 14 Mar 2014 10:51:00 -0000 [thread overview] Message-ID: <bug-60523-4-VQqpduXeia@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60523-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60523 --- Comment #4 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- I would suggest that you implement this as a plugin. Plugins are particularly useful for enforcing this type of coding standards. If you make a generally useful plugin like one enforcing MISRA standards, it could be distributed with GCC in order to serve as a testcase for the plugins framework. >From gcc-bugs-return-446282-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Mar 14 11:16:58 2014 Return-Path: <gcc-bugs-return-446282-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 12902 invoked by alias); 14 Mar 2014 11:16:57 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 12877 invoked by uid 48); 14 Mar 2014 11:16:51 -0000 From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/60525] New: [4.9 Regression] ICE: in final_scan_insn, at final.c:2952 Date: Fri, 14 Mar 2014 11:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: trippels at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter Message-ID: <bug-60525-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-03/txt/msg01151.txt.bz2 Content-length: 2588 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60525 Bug ID: 60525 Summary: [4.9 Regression] ICE: in final_scan_insn, at final.c:2952 Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: trippels at gcc dot gnu.org markus@x4 libgcc % cat test.i typedef struct { long w[2]; } UINT128; extern UINT128 a[]; int b, c, f, g, h, i, l, m, o, p, q; double d; UINT128 j, k, t; long n, r; unsigned long s; fn1 (UINT128 *p1, UINT128 p2, UINT128 p3) { int e; if (p2.w[1]) p1->w[0] = p3.w[0]; e = d + p2.w[0]; if (p3.w[1]) c = e; p1->w[1] = b; } fn2 () { UINT128 u; fn1 (&t, j, k); u = a[l]; int v, w; o = t.w[0] >> 1; w = u.w[1] >> 32; n = t.w[0] * u.w[0]; q = r; r = r + s + (n >> 32); v = q + r >> 1; r = o * u.w[0]; q = o * w; r = r + s + (n >> 32); m = q + r; p = u.w[1] >> 32; r = u.w[1]; s = 0; r = r + t.w[1] + n; i = v; o = t.w[0]; h = k.w[1] * k.w[0]; g = j.w[1]; f = j.w[0]; } markus@x4 libgcc % gcc -march=amdfam10 -O2 -c test.i test.i: In function ‘fn2’: test.i:47:1: error: could not split insn } ^ (insn:TI 31 30 32 5 (parallel [ (set (reg:DF 22 xmm1 [orig:142 D.1904 ] [142]) (float:DF (mem/c:DI (plus:DI (reg/f:DI 7 sp) (const_int -16 [0xfffffffffffffff0])) [7 %sfp+-16 S8 A64]))) (clobber (mem/c:DI (plus:DI (reg/f:DI 7 sp) (const_int -8 [0xfffffffffffffff8])) [0 S8 A64])) ]) test.i:16 219 {*floatdidf2_sse_with_temp} (nil)) test.i:47:1: internal compiler error: in final_scan_insn, at final.c:2952 0x82e4c8 _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) ../../gcc/gcc/rtl-error.c:109 0x6a9d5a final_scan_insn(rtx_def*, _IO_FILE*, int, int, int*) ../../gcc/gcc/final.c:2952 0x6a9fb6 final(rtx_def*, _IO_FILE*, int) ../../gcc/gcc/final.c:2023 0x6aa1e5 rest_of_handle_final ../../gcc/gcc/final.c:4427 0x6aa1e5 execute ../../gcc/gcc/final.c:4502 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <http://gcc.gnu.org/bugs.html> for instructions. {standard input}: Assembler messages: {standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive >From gcc-bugs-return-446283-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Mar 14 11:30:47 2014 Return-Path: <gcc-bugs-return-446283-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 22672 invoked by alias); 14 Mar 2014 11:30:46 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 22638 invoked by uid 48); 14 Mar 2014 11:30:43 -0000 From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/60525] [4.9 Regression] ICE: in final_scan_insn, at final.c:2952 Date: Fri, 14 Mar 2014 11:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: trippels at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: <bug-60525-4-yGvT4NZffb@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-60525-4@http.gcc.gnu.org/bugzilla/> References: <bug-60525-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-03/txt/msg01152.txt.bz2 Content-length: 413 http://gcc.gnu.org/bugzilla/show_bug.cgi?id`525 Markus Trippelsdorf <trippels at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rth at gcc dot gnu.org --- Comment #1 from Markus Trippelsdorf <trippels at gcc dot gnu.org> --- Started with r208556.
next prev parent reply other threads:[~2014-03-14 10:51 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-60523-4@http.gcc.gnu.org/bugzilla/> 2014-03-14 8:58 ` pinskia at gcc dot gnu.org 2014-03-14 10:39 ` david at westcontrol dot com 2014-03-14 10:51 ` manu at gcc dot gnu.org [this message] 2014-03-14 11:31 ` david at westcontrol dot com 2022-08-29 23:25 ` [Bug c/60523] Warning flag for octal literals [-Woctal-literals] f.heckenbach@fh-soft.de
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-60523-4-VQqpduXeia@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).