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 middle-end/55404] [4.8 Regression] Lots of failures at -O3 Date: Tue, 20 Nov 2012 00:03:00 -0000 [thread overview] Message-ID: <bug-55404-4-pU1AoxqW2Y@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55404-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55404 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-11-20 00:03:31 UTC --- *overlap_iterations_a = conflict_fn (1, affine_fn_cst (integer_zero_node)); static conflict_function * conflict_fn (unsigned n, ...) static affine_fn affine_fn_cst (tree cst) tree-data-ref.h:typedef vec<tree> affine_fn; So yes this is the same issue as PR 55398 in the end. *** This bug has been marked as a duplicate of bug 55398 ***
prev parent reply other threads:[~2012-11-20 0:03 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-19 23:56 [Bug middle-end/55404] New: " pinskia at gcc dot gnu.org 2012-11-19 23:59 ` [Bug middle-end/55404] " pinskia at gcc dot gnu.org 2012-11-20 0:03 ` pinskia at gcc dot gnu.org [this message]
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-55404-4-pU1AoxqW2Y@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).