Hello,
I've been scratching my head over an implicit conversion issue,
depicted in the following code:
typedef __attribute__ ((vector_size(4 * sizeof(int int generic_int32x4;
struct Foo {
Foo() {
}
Foo(const generic_int32x4& src) {
}
operator generic_int32x4() const {
Hi Marc,
Thank you for the reply. So it's a known g++ issue with a candidate
patch. Looking at the patch, I was wondering, what precludes the
generic vector types form being proper arithmetic types?
Regards,
Martin
On 26 May 2016 at 09:02, Marc Glisse wrote:
> On Thu, 26 May 2016
wrote:
> On Thu, 26 May 2016, martin krastev wrote:
>
>> Thank you for the reply. So it's a known g++ issue with a candidate
>> patch. Looking at the patch, I was wondering, what precludes the
>> generic vector types form being proper arithmetic types?
>
>
>
Hello,
I'm trying to build gcc-7.3.0 (md5 747d5010b7c6938b480bc6e4d7c4be9a of
tar.gz) natively on a MACHTYPE=mipsel-unknown-linux-gnu MIPS p5600 machine
under Debian Stretch. I'm getting an illegal instruction during libstdc++
build phase:
libtool: compile: /home/gru/proj/gcc_build/./gcc/xgcc -s
gcc version: powerpc-apple-darwin8.11.0-gcc-4.4.0 (GCC) 4.4.0 20090116
(experimental)
version is a macports (formerly darwin ports) build of gcc4.4.0 on an
OSX 10.4.11 ppc7450 host
Following C function produces different code depending on the use of
'loop_Ai' vs 'direct_assignment_Ai' snippets:
f
