From: Eric Botcazou <ebotcazou@adacore.com>
To: gcc-patches@gcc.gnu.org
Cc: Bernd Schmidt <bschmidt@redhat.com>
Subject: Re: [patch] Fix PR middle-end/68291 & 68292
Date: Mon, 07 Dec 2015 16:42:00 -0000 [thread overview]
Message-ID: <1582891.0dDj8qRMGV@polaris> (raw)
In-Reply-To: <56655C0F.3090704@redhat.com>
> Ok. Although thinking about your comment in the PR about not making such
> vectors gimple registers I wonder what the effects of that would be.
First of all it's a bit painful to do because is_gimple_reg_type is defined
inline in gimple-expr.h and adding TYPE_MODE in there causes a compilation
failure for a bunch of files. More seriously, this can probably be seen as a
real layering violation so I'm not sure this would be a progress.
--
Eric Botcazou
next prev parent reply other threads:[~2015-12-07 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 9:36 Eric Botcazou
2015-12-07 10:14 ` Bernd Schmidt
2015-12-07 16:42 ` Eric Botcazou [this message]
2015-12-07 17:01 ` Richard Biener
2015-12-08 9:31 ` Christophe Lyon
2015-12-08 9:46 ` Eric Botcazou
2015-12-08 10:05 ` Christophe Lyon
2015-12-08 10:50 ` Eric Botcazou
2015-12-08 15:40 ` Bernd Schmidt
2015-12-08 18:48 ` Eric Botcazou
2015-12-09 9:11 ` Christophe Lyon
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=1582891.0dDj8qRMGV@polaris \
--to=ebotcazou@adacore.com \
--cc=bschmidt@redhat.com \
--cc=gcc-patches@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).