David Edelsohn <[EMAIL PROTECTED]> wrote on 02.03.2007 19:10:58:
> > Devang Patel writes:
>
> >> Is there a reason why op0 is V4SF
> Devang> It is destination so, yes this is wrong.
>
> >> and op1 is V4SI (and not V8HI)?
>
> Devang> condition should be v4si, but it is not op1. So this is al
I noticed that in fortran/convert.c the convert() function calls
convert_to_vector() if the target type is VECTOR_TYPE. When is that
function triggered in Fortran frontend? Since Fortran language doesn't
support vector type, why does it convert something to a vector expression?
Thanks!
Sa
Hi,
I'm working on GCC 4.1.1 on spu target and get following problem:
After splitting an insn with a note REG_LIBCALL, the insn is replaced by
some other insns, which don't attach REG_LIBCALL note any more, and the
original one is then deleted. While the insn REG_RETVAL still points to
the LIB
Hi all,
I have detected a bug in C++ frontend.
When compiling a function with parameter of a pointer to a vector constant
type, the compiler calls a recursive function and is not able to get out.
Concretely, in gcc/cp/mangle.c file, in function write_type:
if (write_CV_qualifiers_for_type
"Andrew Pinski" <[EMAIL PROTECTED]> wrote on 02.08.2007 19:36:30:
> This used to work. Can you file a bug at the very least?
>
> Thanks,
> Andrew Pinski
I have opened a bug against it.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32970
Sa
Ian Lance Taylor <[EMAIL PROTECTED]> wrote on 03.08.2007 17:24:45:
> Thanks. The general idea looks right, but the implementation is
> incorrect.
>
Thank you! I have made the correction:
Index: gcc/emit-rtl.c
===
--- gcc.orig/emit
Ian Lance Taylor <[EMAIL PROTECTED]> wrote on 30.07.2007 18:59:28:
> If the compiler splits an insn with a REG_LIBCALL note, it needs to
> remove the corresponding REG_RETVAL note, or it needs to relink the
> insns. This looks like a compiler bug, in that try_split doesn't
> handle REG_LIBCALL no
"Andrew Pinski" <[EMAIL PROTECTED]> wrote on 02.08.2007 19:36:30:
> On 8/2/07, Sa Liu <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> > I have detected a bug in C++ frontend.
>
> This used to work. Can you file a bug at the very least?
>
Hi
