The following invalid code snippet triggers an ICE since GCC 4.0.0:
=
int __attribute__((vector_size(8))) main()
{
return 0;
}
=
bug.cc:1: internal compiler error: in start_function, at cp/decl.c:107
--- Comment #33 from vincent at vinc17 dot org 2006-11-05 23:27 ---
(In reply to comment #32)
> (In reply to comment #31)
> > (In reply to comment #30)
> > So, I don't think a mpfr_signgam alone would really be useful. So, I think
> > that
> > choice 2 would be better.
>
> Okay, sounds
--
reichelt at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.0.4
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29735
The following invalid code snippet triggers an ICE since GCC 4.0.2:
=
int __attribute__((vector_size(8),vector_size(8))) v;
void foo()
{
v = v + v;
}
=
bug.c: In function 'foo':
bug.c:5: internal
--
reichelt at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.0.4
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29736
--- Comment #49 from chuck at vertica dot com 2006-11-05 23:39 ---
Sorry.
But maybe it is a FAQ because even with "-Wall" or "-Wstrict-aliasing=2" g++
4.0.2 generates invalid code for this without so much as a peep. I here 4.1 is
better about giving a warning.
I guess it was too much
--- Comment #2 from mckelvey at maskull dot com 2006-11-06 00:35 ---
OK, that fixed the problem. But shouldn't configuration have caught it?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29720
--- Comment #9 from dave at hiauly1 dot hia dot nrc dot ca 2006-11-06
00:43 ---
Subject: Re: jc1: out of memory allocating 4072 bytes after a total of
708630224 bytes
> So this ends up being what i thought. The variables aren't being
> collapsed, but i can't figure out why (IE it can
Latest CVS, builds fine. Attempt to "make check" yields:
gmake[1]: Entering directory `/usr/home/mckelvey/software/gcc-obj'
gmake[2]: Entering directory `/usr/home/mckelvey/software/gcc-obj/fixincludes'
autogen -T ../../gcc/fixincludes/check.tpl ../../gcc/fixincludes/inclhack.def
/bin/sh ./check.s
--- Comment #3 from daney at gcc dot gnu dot org 2006-11-06 01:17 ---
Manually moving the
lw $4,%got($L2406)($28)
to be just before the
addiu $4,$4,%lo($L2406)
and reassembling fixes the problem.
So I think that my analysis about the problem being splitting them up with
--- Comment #5 from bdavis at gcc dot gnu dot org 2006-11-06 04:10 ---
patch here:
http://gcc.gnu.org/ml/fortran/2006-11/msg00148.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28974
--- Comment #2 from patchapp at dberlin dot org 2006-11-06 06:41 ---
Subject: Bug number PR c++/29573
A patch for this bug has been added to the patch tracker.
The mailing list url for the patch is
http://gcc.gnu.org/ml/gcc-patches/2006-10/msg01746.html
--
http://gcc.gnu.org/bugzil
101 - 112 of 112 matches
Mail list logo