From: tbp <tbptbp@gmail.com>
To: gcc@gcc.gnu.org
Subject: Re: gcc/g++ 4.0.0, 20041205 snapshot, bug #18073 still present
Date: Tue, 07 Dec 2004 14:21:00 -0000 [thread overview]
Message-ID: <4fc48eb104120706212dfbb1d6@mail.gmail.com> (raw)
In-Reply-To: <4fc48eb104120612413d6affc3@mail.gmail.com>
Hmm.
I don't know what i'm supposed to do with a bug marked as resolved
when it's not.
I've added an entry http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18073
some days ago, and got no sign of life.
So i've reposted here, to no avail.
Am i supposed to open a new bug in bugzilla?
If someone in the know could just give me some clue about what i'm
doing wrong, i'll happily do my best to get that covered (like "it's
known, move on" or "give more info, stupid" or "we don't give a rat's
ass" etc).
Thanks in advance.
On Mon, 6 Dec 2004 21:41:50 +0100, tbp <tbptbp@gmail.com> wrote:
> Unsure if it's a known issue, it's marked as resolved, yet on cygwin i get:
> /usr/local/gcc-405/lib/gcc/i686-pc-cygwin/4.0.0/include/mmintrin.h: In
> function 'int _mm_cvtsi64_si32(int __vector__)':
> /usr/local/gcc-405/lib/gcc/i686-pc-cygwin/4.0.0/include/mmintrin.h:91:
> error: invalid cast from type 'int __vector__' to type 'long long int'
> /usr/local/gcc-405/lib/gcc/i686-pc-cygwin/4.0.0/include/mmintrin.h: In
> function 'int __vector__ _mm_add_si64(int __vector__, int
> __vector__)':
> /usr/local/gcc-405/lib/gcc/i686-pc-cygwin/4.0.0/include/mmintrin.h:282:
> error: invalid cast from type 'int __vector__' to type 'long long int'
> /usr/local/gcc-405/lib/gcc/i686-pc-cygwin/4.0.0/include/mmintrin.h:282:
> error: invalid cast from type 'int __vector__' to type 'long long int'
> /usr/local/gcc-405/lib/gcc/i686-pc-cygwin/4.0.0/include/mmintrin.h: In
> function 'int __vector__ _mm_sub_si64(int __vector__, int
> __vector__)':
>
> Also present in the 20041128 snapshot etc... in fact i have to ressort
> to the 20041017 snapshot because of it.
> That's annoying because gcc4 produce by far the best SSE code (when
> you can dodge ICEs) and that's pretty critical in my current project.
>
> Reading specs from /usr/local/gcc-405/lib/gcc/i686-pc-cygwin/4.0.0/specs
> Configured with: ../configure --prefix=/usr/local/gcc-405
> --enable-languages=c,c++ --enable-threads=posix --with-system-zlib
> --disable-checking --disable-nls --disable-shared
> --disable-win32-registry --verbose --with-gcc --with-gnu-ld
> --with-gnu-as --with-as=/usr/local/binutils/bin/as
> --with-ld=/usr/local/binutils/bin/ld
> Thread model: posix
> gcc version 4.0.0 20041205 (experimental)
>
next prev parent reply other threads:[~2004-12-07 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 20:42 tbp
2004-12-07 14:21 ` tbp [this message]
2004-12-07 16:12 ` Nathan Sidwell
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=4fc48eb104120706212dfbb1d6@mail.gmail.com \
--to=tbptbp@gmail.com \
--cc=gcc@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).