This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Vector problems with GCC 3.4
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: mark at codesourcery dot com
- Cc: gcc at gcc dot gnu dot org, Andrew Pinski <pinskia at physics dot uc dot edu>, aldyh at redhat dot com
- Date: Sun, 29 Feb 2004 18:59:50 -0800
- Subject: Re: Vector problems with GCC 3.4
- References: <200403010229.i212TOSx010027@sirius.codesourcery.com>
On Feb 29, 2004, at 18:29, Mark Mitchell wrote:
Aldy --
There are three PRs relating to problems with vector instructions in
GCC 3.4:
Well this one needs a debuging (really dwarf-2) expect as it is the
question here
is how should const_vector be represented in dwarf-2/3:
PR 11983
The question with this one is should we be rejecting the compare if not
should we
be supplying the corresponding generic infrastructure:
PR 14219
This is an x86 problem and not related to vectors at all really, it
most likely also fails
in 3.3.3 which I did not test:
PR 14343
(Also note I think the previous PR was caused by:
2004-01-09 Richard Henderson <rth@redhat.com>
* recog.c (constrain_operands): Validate mem operands.
But is laten target bug. )
Thanks,
Andrew Pinski