-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/08/11 07:33, Michael Matz wrote:
> Hi,
>
> the problem is that some initializers expand to loops. If such
> initializers are inserted on edges we have looping control flow on them.
> Even if we have no loops, but normal control flow on them
On Fri, Apr 8, 2011 at 6:58 AM, Michael Matz wrote:
> Hi,
>
> On Fri, 8 Apr 2011, Jakub Jelinek wrote:
>
>> On Fri, Apr 08, 2011 at 03:33:49PM +0200, Michael Matz wrote:
>> > --- testsuite/gcc.target/i386/pr48389.c (revision 0)
>> > +++ testsuite/gcc.target/i386/pr48389.c (revision 0)
>> >
On Fri, Apr 08, 2011 at 03:58:57PM +0200, Michael Matz wrote:
> But then I'd have to use --target_board to hit the original problem.
That isn't so a big deal, testing with
RUNTESTFLAGS='--target_board=unix\{-m32,-m64\}'
is what people do very often. Or just do a 32-bit instead of 64-bit
bootstr
Hi,
On Fri, 8 Apr 2011, Jakub Jelinek wrote:
> On Fri, Apr 08, 2011 at 03:33:49PM +0200, Michael Matz wrote:
> > --- testsuite/gcc.target/i386/pr48389.c (revision 0)
> > +++ testsuite/gcc.target/i386/pr48389.c (revision 0)
> > @@ -0,0 +1,12 @@
> > +/* PR middle-end/48389 */
> > +/* { dg-d
On Fri, Apr 08, 2011 at 03:33:49PM +0200, Michael Matz wrote:
> --- testsuite/gcc.target/i386/pr48389.c (revision 0)
> +++ testsuite/gcc.target/i386/pr48389.c (revision 0)
> @@ -0,0 +1,12 @@
> +/* PR middle-end/48389 */
> +/* { dg-do compile } */
> +/* { dg-options "-O -m32 -mtune=penti
Hi,
the problem is that some initializers expand to loops. If such
initializers are inserted on edges we have looping control flow on them.
Even if we have no loops, but normal control flow on them (which can
happen in other situations) we still forget to initialize JUMP_LABEL on
them leadin
