public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tim Prince <timothyprince@sbcglobal.net>
To: ranjith kumar <ranjit_kumar_b4u@yahoo.co.uk>
Cc: gcc-help@gcc.gnu.org
Subject: Re: compilation error
Date: Sat, 07 Oct 2006 19:36:00 -0000	[thread overview]
Message-ID: <452801A3.60505@sbcglobal.net> (raw)
In-Reply-To: <20061007185828.17176.qmail@web27408.mail.ukl.yahoo.com>

ranjith kumar wrote:
> Hi,
> -------------------------------------------------------
> #include <mmintrin.h>
> int  main()
> {
>    __m64 m1 = 0x00ff00a300bc00ae;
>    __m64 m2 = 0x0001000100010001;
>  __m64 m3;
>    unsigned char *data;
>    unsigned char ch;
>    int i;
> //asm ("pmaddwd m1,m2\n\t");
>    m3 =_mm_madd_pi16 (m1, m2);
>    printf("value is %x%x\n", m1);
>    printf("value is %x%x\n", m2);
>    printf("value is %x%x\n", m3);
> data = (char *)&m3;
>    for ( i = 0; i < 8; i++)
>         {
>         printf("Element %d value is %x\n", i,
> data[i]);
>         }
>    return;
> }
> ------------------------------------------------------
> I got the following error when I compiled the above
> program with gcc 4.0.0 compiler on pentium4 processor.
> The compilation command :
>  gcc -march=pentium4 sample.c
> ----------------------------------------------
> sample.c: In function `main':
> sample.c:7: invalid initializer
> sample.c:8: invalid initializer
> ----------------------------------------------

Does it make a difference if you add LL suffix?  Without that, your 
constant is implicitly typed int.  Not that I can buy in to whatever 
you're trying to do.

  reply	other threads:[~2006-10-07 19:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-07 18:58 ranjith kumar
2006-10-07 19:36 ` Tim Prince [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-08-15 15:43 Configuration Error Jonathan Wakely
2012-08-15 17:49 ` B B
2012-08-15 17:57   ` Jonathan Wakely
2012-08-15 18:03     ` Compilation Error Ron Stubbs
2012-08-15 18:14       ` Marc Glisse
2012-08-15 18:46       ` B B
     [not found]         ` <CAH6eHdRV5NLCO-+iJw1FHqw+6EV-LSCNkhF-SJ0jZUPtdbwFKQ@mail.gmail.com>
2012-08-15 19:25           ` Jonathan Wakely
2012-08-15 19:36     ` Ron Stubbs
2012-08-16  3:59       ` Marc Glisse
2012-08-16 13:29         ` Ron Stubbs
2012-08-16 15:15           ` Tim Prince
2012-08-16 20:06           ` Marc Glisse
2012-08-17  0:12             ` Ron Stubbs
2012-08-17  7:23               ` Marc Glisse
2012-08-17  8:23                 ` Jonathan Wakely
2011-06-08 12:25 compilation error Rony Paul
2011-06-08 13:31 ` Jonathan Wakely
2011-06-08 13:47 ` Ian Lance Taylor
2005-07-18  4:24 Compilation error Oleg Kotsyurbiy
2005-07-18  5:51 ` Ian Lance Taylor
2005-07-18  7:45   ` Arturas Moskvinas
2000-02-21 10:27 Jose Miguel A.C.Pires
2000-02-21 10:39 ` llewelly
2000-04-01  0:00   ` llewelly
2000-04-01  0:00 ` Jose Miguel A.C.Pires

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=452801A3.60505@sbcglobal.net \
    --to=timothyprince@sbcglobal.net \
    --cc=gcc-help@gcc.gnu.org \
    --cc=ranjit_kumar_b4u@yahoo.co.uk \
    --cc=tprince@myrealbox.com \
    /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).