public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "antoine.balestrat at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/59020] [4.9 Regression] internal compiler error: in maybe_add_or_update_dep_1, at sched-deps.c:933 Date: Sat, 23 Nov 2013 20:24:00 -0000 [thread overview] Message-ID: <bug-59020-4-G9Ll1rmSk1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59020-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59020 Antoine Balestrat <antoine.balestrat at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |antoine.balestrat at gmail dot com --- Comment #3 from Antoine Balestrat <antoine.balestrat at gmail dot com> --- I've got a short C testcase if this is of any help. $ cat fail.c int a, b, d; unsigned c; void f() { unsigned q; for(; a; a++) if(((c %= d && 1) ? : 1) & 1) for(; b; q++); } $ xgcc -w -march=native -O2 -fmodulo-sched fail.c fail.c: In function 'f': fail.c:10:1: internal compiler error: in maybe_add_or_update_dep_1, at sched-deps.c:933 } ^ Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. Using gcc 4.9 as of 20131123.
next prev parent reply other threads:[~2013-11-23 20:24 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-06 10:53 [Bug rtl-optimization/59020] New: " Joost.VandeVondele at mat dot ethz.ch 2013-11-06 10:54 ` [Bug rtl-optimization/59020] " Joost.VandeVondele at mat dot ethz.ch 2013-11-06 11:38 ` rguenth at gcc dot gnu.org 2013-11-19 14:19 ` rguenth at gcc dot gnu.org 2013-11-23 20:24 ` antoine.balestrat at gmail dot com [this message] 2013-11-24 0:33 ` hjl.tools at gmail dot com 2013-12-03 18:35 ` wmi at gcc dot gnu.org 2013-12-04 10:09 ` Joost.VandeVondele at mat dot ethz.ch
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-59020-4-G9Ll1rmSk1@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).