This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: ICE in trunk due to MEM with address in vector mode
- From: Richard Sandiford <rdsandiford at googlemail dot com>
- To: Paulo Matos <pmatos at broadcom dot com>
- Cc: "gcc\ at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Fri, 24 Jan 2014 16:33:52 +0000
- Subject: Re: ICE in trunk due to MEM with address in vector mode
- Authentication-results: sourceware.org; auth=none
- References: <19EB96622A777C4AB91610E763265F463EED53 at SJEXCHMB14 dot corp dot ad dot broadcom dot com> <87zjmlr72j dot fsf at sandifor-thinkpad dot stglab dot manchester dot uk dot ibm dot com> <19EB96622A777C4AB91610E763265F463EF48B at SJEXCHMB14 dot corp dot ad dot broadcom dot com> <87ob31r2op dot fsf at sandifor-thinkpad dot stglab dot manchester dot uk dot ibm dot com> <19EB96622A777C4AB91610E763265F463EF82A at SJEXCHMB14 dot corp dot ad dot broadcom dot com>
Paulo Matos <pmatos@broadcom.com> writes:
>> If we do support vector addresses than I think the right fix is to
>> check VECTOR_MODE_P there.
>
> Well, isn't it the case that a mem with vector mode is always mode
> dependent, in which case adding VECTOR_MODE_P to mode-dependent target
> hook would be enough making the patch not so useful?
Yeah, adding it to the target hook would work too. I'd just prefer it
to be in generic code because I think it's a target-independent rule.
I can see that for an out-of-tree port it would be easier to put it in
the target hook though.
Thanks,
Richard