public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/63986] [5 Regression][SH] gcc.target/sh/pr51244-15.c failures
Date: Thu, 20 Nov 2014 18:15:00 -0000 [thread overview]
Message-ID: <bug-63986-4-C2320o3YqG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63986-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63986
--- Comment #7 from Oleg Endo <olegendo at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #1)
> I think you were mostly lucky
And exactly that's why I'd better not rely on combine dreaming up the parallel
pattern if I want to control the instruction (sequence) selection in a more
reliable way.
I didn't mean to file this PR as tree-optimization, but rather as a target
issue.
next prev parent reply other threads:[~2014-11-20 18:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 3:51 [Bug tree-optimization/63986] New: " olegendo at gcc dot gnu.org
2014-11-20 9:55 ` [Bug tree-optimization/63986] " rguenth at gcc dot gnu.org
2014-11-20 9:57 ` rguenth at gcc dot gnu.org
2014-11-20 11:42 ` ebotcazou at gcc dot gnu.org
2014-11-20 13:13 ` ppalka at gcc dot gnu.org
2014-11-20 13:29 ` rguenther at suse dot de
2014-11-20 18:15 ` olegendo at gcc dot gnu.org [this message]
2014-11-21 8:29 ` [Bug target/63986] " rguenth at gcc dot gnu.org
2014-11-22 6:40 ` olegendo at gcc dot gnu.org
2014-11-22 15:07 ` olegendo at gcc dot gnu.org
2014-11-25 6:46 ` olegendo at gcc dot gnu.org
2014-12-01 6:50 ` olegendo at gcc dot gnu.org
2014-12-10 15:32 ` rguenth at gcc dot gnu.org
2014-12-10 20:36 ` olegendo 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-63986-4-C2320o3YqG@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: link
Be 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).