public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/35049] [4.3 Regression] g++.dg/conversion/simd3.C:12: error: invalid operands to binary + (have 'float __vector__' and 'int __vector__')
Date: Fri, 01 Feb 2008 10:29:00 -0000	[thread overview]
Message-ID: <20080201102855.22919.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35049-12313@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from rguenth at gcc dot gnu dot org  2008-02-01 10:28 -------
Regressions should have a target milestone.

But -- this error is expected?  For reference:

/* { dg-do compile } */

typedef int myint;

float __attribute__((vector_size(16))) b;
int __attribute__((vector_size(16))) d;
myint __attribute__((vector_size(16))) d2;
unsigned int __attribute__((vector_size(16))) e;

void foo()
{
        b + d; /* { dg-error "invalid operands to binary" } */
        d += e; /* { dg-error "use -flax-vector-conversions to permit
conversions between vectors with differing element types or numbers of
subparts.*cannot convert 'unsigned int __vector__' to 'int __vector__' in
assignment" } */
        d2 += d;
}

so, can you paste the full log of this FAIL?


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |4.3.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35049


  reply	other threads:[~2008-02-01 10:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01  9:38 [Bug c++/35049] New: " dominiq at lps dot ens dot fr
2008-02-01 10:29 ` rguenth at gcc dot gnu dot org [this message]
2008-02-01 11:32 ` [Bug c++/35049] " dominiq at lps dot ens dot fr
2008-02-01 11:34 ` pinskia at gcc dot gnu dot org
2008-02-01 18:11 ` pinskia at gcc dot gnu dot org
2008-02-01 18:40 ` hjl dot tools at gmail dot com
2008-02-01 18:49 ` hjl dot tools at gmail dot com
2008-02-04 22:51 ` rguenth at gcc dot gnu dot org
2008-02-05 14:35 ` dgregor at gcc dot gnu dot org
2008-02-05 18:07 ` dgregor at gcc dot gnu dot org
2008-02-06 15:19 ` dgregor at gcc dot gnu dot org
2008-02-06 18:05 ` pinskia at gcc dot gnu dot org
2008-02-06 18:50 ` dgregor at gcc dot gnu dot org
2008-02-06 18:51 ` dgregor at gcc dot gnu dot org
2008-02-07 10:10 ` bonzini at gnu dot org
2008-02-07 13:12 ` bonzini at gnu dot org
2008-03-07 11:48 ` bonzini at gcc dot gnu dot org

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=20080201102855.22919.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).