public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* [tree-ssa] Mainline merge as of 2004-03-24
@ 2004-03-26 18:22 Diego Novillo
  2004-03-26 18:37 ` law
  0 siblings, 1 reply; 2+ messages in thread
From: Diego Novillo @ 2004-03-26 18:22 UTC (permalink / raw)
  To: gcc


Bootstrapped and tested x86, x86-64 and alpha.  We have new c-torture
regressions that are not present in mainline:

         FAIL: gcc.c-torture/execute/20040313-1.c execution
         FAIL: gcc.c-torture/execute/20040313-1.c execution
         FAIL: gcc.c-torture/execute/20040313-1.c execution
         FAIL: gcc.c-torture/execute/20040313-1.c execution
         FAIL: gcc.c-torture/execute/20040313-1.c execution
         FAIL: gcc.c-torture/execute/20040313-1.c execution
         FAIL: gcc.c-torture/execute/loop-2c.c execution
         FAIL: gcc.c-torture/execute/loop-2d.c execution
         FAIL: gcc.dg/torture/builtin-nonneg-1.c (test for excess errors)
         FAIL: gcc.dg/torture/builtin-nonneg-1.c (test for excess errors)
         FAIL: gcc.dg/torture/builtin-nonneg-1.c (test for excess errors)
         FAIL: gcc.dg/torture/builtin-nonneg-1.c (test for excess errors)
         FAIL: gcc.dg/torture/builtin-nonneg-1.c (test for excess errors)
         FAIL: gcc.dg/torture/builtin-nonneg-1.c (test for excess errors)

20040313-1.c is the test case for PR 14470.  The two loop failures
happen only at -Os on x86, it does not seem to be a tree optimizer
failure because we emit the same trees.  I'm looking at those today. 
The builtin-nonneg failure is another case of tree-ssa not folding
builtins properly.

None of the failures seemed important enough to hold the merge which was
already getting old.


Diego.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [tree-ssa] Mainline merge as of 2004-03-24
  2004-03-26 18:22 [tree-ssa] Mainline merge as of 2004-03-24 Diego Novillo
@ 2004-03-26 18:37 ` law
  0 siblings, 0 replies; 2+ messages in thread
From: law @ 2004-03-26 18:37 UTC (permalink / raw)
  To: Diego Novillo; +Cc: gcc

In message <1080318686.4600.141.camel@localhost.localdomain>, Diego Novillo wri
tes:
 >
 >Bootstrapped and tested x86, x86-64 and alpha.  We have new c-torture
 >regressions that are not present in mainline:
 >
 >         FAIL: gcc.c-torture/execute/20040313-1.c execution
 >         FAIL: gcc.c-torture/execute/20040313-1.c execution
 >         FAIL: gcc.c-torture/execute/20040313-1.c execution
 >         FAIL: gcc.c-torture/execute/20040313-1.c execution
 >         FAIL: gcc.c-torture/execute/20040313-1.c execution
 >         FAIL: gcc.c-torture/execute/20040313-1.c execution
 >         FAIL: gcc.c-torture/execute/loop-2c.c execution
 >         FAIL: gcc.c-torture/execute/loop-2d.c execution
 >         FAIL: gcc.dg/torture/builtin-nonneg-1.c (test for excess errors)
 >         FAIL: gcc.dg/torture/builtin-nonneg-1.c (test for excess errors)
 >         FAIL: gcc.dg/torture/builtin-nonneg-1.c (test for excess errors)
 >         FAIL: gcc.dg/torture/builtin-nonneg-1.c (test for excess errors)
 >         FAIL: gcc.dg/torture/builtin-nonneg-1.c (test for excess errors)
 >         FAIL: gcc.dg/torture/builtin-nonneg-1.c (test for excess errors)
 >
 >20040313-1.c is the test case for PR 14470.  The two loop failures
 >happen only at -Os on x86, it does not seem to be a tree optimizer
 >failure because we emit the same trees.  I'm looking at those today. 
 >The builtin-nonneg failure is another case of tree-ssa not folding
 >builtins properly.
 >
 >None of the failures seemed important enough to hold the merge which was
 >already getting old.
Agreed.
jeff


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-03-26 16:44 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-03-26 18:22 [tree-ssa] Mainline merge as of 2004-03-24 Diego Novillo
2004-03-26 18:37 ` law

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).