--- Comment #8 from pinskia at gcc dot gnu dot org 2007-04-30 18:02 ---
Fixed.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Status|ASSIGNED
--- Comment #7 from pinskia at gcc dot gnu dot org 2007-04-30 18:01 ---
Subject: Bug 31721
Author: pinskia
Date: Mon Apr 30 18:01:18 2007
New Revision: 124300
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=124300
Log:
2007-04-30 Andrew Pinski <[EMAIL PROTECTED]>
PR C+
--- Comment #6 from pinskia at gcc dot gnu dot org 2007-04-29 07:44 ---
Sorry Timothy, if this bug took too long to fix, it seems like many people were
not using the vector extension with C++ that much so nobody actually looked
into it until now. I only looked into it because I found th
--- Comment #5 from pinskia at gcc dot gnu dot org 2007-04-27 02:46 ---
In fact we should be using more than just build_reference_type, we should be
using build_reference_type_for_mode.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31721
--- Comment #4 from pinskia at gcc dot gnu dot org 2007-04-27 02:11 ---
This has been broken since the patch went in to support vector_size, see:
http://gcc.gnu.org/ml/gcc-patches/2001-12/msg00778.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31721
--- Comment #3 from pinskia at gcc dot gnu dot org 2007-04-27 01:55 ---
The problem is obvious.
reconstruct_complex_type looks at POINTER_TYPE_P but it does not check which
case (pointer or reference) it should be building and just calls
build_pointer_type always which is wrong.
--
p
--- Comment #2 from pinskia at gcc dot gnu dot org 2007-04-27 01:12 ---
Confirmed via the duplicated bug.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-04-27 01:11 ---
*** Bug 14217 has been marked as a duplicate of this bug. ***
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
---
