public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug regression/16429] New: [regression 3.5] New fails for gcc.c-torture/execute/20020412-1.c
@ 2004-07-08  1:44 danglin at gcc dot gnu dot org
  2004-07-08  2:36 ` [Bug regression/16429] [3.5 regression] gcc.c-torture/execute/20020412-1.c fails pinskia at gcc dot gnu dot org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: danglin at gcc dot gnu dot org @ 2004-07-08  1:44 UTC (permalink / raw)
  To: gcc-bugs

Executing on host: /xxx/gnu/gcc-3.3/objdir/gcc/xgcc -B/xxx/gnu/gcc-3.3/objdir/gc
c/ /xxx/gnu/gcc-3.3/gcc/gcc/testsuite/gcc.c-torture/execute/20020412-1.c  -w  -O
0   -lm   -o /xxx/gnu/gcc-3.3/objdir/gcc/testsuite/20020412-1.x0    (timeout = 3
00)
/xxx/gnu/gcc-3.3/gcc/gcc/testsuite/gcc.c-torture/execute/20020412-1.c: In functi
on `foo':
/xxx/gnu/gcc-3.3/gcc/gcc/testsuite/gcc.c-torture/execute/20020412-1.c:30: intern
al compiler error: in create_tmp_var, at gimplify.c:358
Please submit a full bug report,
with preprocessed source if appropriate.

-- 
           Summary: [regression 3.5] New fails for gcc.c-
                    torture/execute/20020412-1.c
           Product: gcc
           Version: 3.5.0
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: regression
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: danglin at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: hppa64-hp-hpux11.11
  GCC host triplet: hppa64-hp-hpux11.11
GCC target triplet: hppa64-hp-hpux11.11


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16429


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

* [Bug regression/16429] [3.5 regression] gcc.c-torture/execute/20020412-1.c fails
  2004-07-08  1:44 [Bug regression/16429] New: [regression 3.5] New fails for gcc.c-torture/execute/20020412-1.c danglin at gcc dot gnu dot org
@ 2004-07-08  2:36 ` pinskia at gcc dot gnu dot org
  2004-07-08  2:50 ` dave at hiauly1 dot hia dot nrc dot ca
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2004-07-08  2:36 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-07-08 02:35 -------
Can you try again because it was failuring on July 1 but started to pass on the July 2.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |ice-on-valid-code
            Summary|[regression 3.5] New fails  |[3.5 regression] gcc.c-
                   |for gcc.c-                  |torture/execute/20020412-1.c
                   |torture/execute/20020412-1.c|fails
   Target Milestone|---                         |3.5.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16429


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

* [Bug regression/16429] [3.5 regression] gcc.c-torture/execute/20020412-1.c fails
  2004-07-08  1:44 [Bug regression/16429] New: [regression 3.5] New fails for gcc.c-torture/execute/20020412-1.c danglin at gcc dot gnu dot org
  2004-07-08  2:36 ` [Bug regression/16429] [3.5 regression] gcc.c-torture/execute/20020412-1.c fails pinskia at gcc dot gnu dot org
@ 2004-07-08  2:50 ` dave at hiauly1 dot hia dot nrc dot ca
  2004-07-20 15:44 ` pinskia at gcc dot gnu dot org
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: dave at hiauly1 dot hia dot nrc dot ca @ 2004-07-08  2:50 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From dave at hiauly1 dot hia dot nrc dot ca  2004-07-08 02:50 -------
Subject: Re:  [3.5 regression] gcc.c-torture/execute/200

> ------- Additional Comments From pinskia at gcc dot gnu dot org  2004-07-08
> 02:35 -------
> Can you try again because it was failuring on July 1 but started to pass on
> the July 2.

It's failing today:

<http://gcc.gnu.org/ml/gcc-testresults/2004-07/msg00316.html>.

Dave


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16429


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

* [Bug regression/16429] [3.5 regression] gcc.c-torture/execute/20020412-1.c fails
  2004-07-08  1:44 [Bug regression/16429] New: [regression 3.5] New fails for gcc.c-torture/execute/20020412-1.c danglin at gcc dot gnu dot org
  2004-07-08  2:36 ` [Bug regression/16429] [3.5 regression] gcc.c-torture/execute/20020412-1.c fails pinskia at gcc dot gnu dot org
  2004-07-08  2:50 ` dave at hiauly1 dot hia dot nrc dot ca
@ 2004-07-20 15:44 ` pinskia at gcc dot gnu dot org
  2004-07-20 16:00 ` dave at hiauly1 dot hia dot nrc dot ca
  2004-07-20 16:04 ` pinskia at gcc dot gnu dot org
  4 siblings, 0 replies; 6+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2004-07-20 15:44 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-07-20 15:44 -------
Does this fail anymore?
It seems like it does not: <http://gcc.gnu.org/ml/gcc-testresults/2004-07/msg00922.html>.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16429


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

* [Bug regression/16429] [3.5 regression] gcc.c-torture/execute/20020412-1.c fails
  2004-07-08  1:44 [Bug regression/16429] New: [regression 3.5] New fails for gcc.c-torture/execute/20020412-1.c danglin at gcc dot gnu dot org
                   ` (2 preceding siblings ...)
  2004-07-20 15:44 ` pinskia at gcc dot gnu dot org
@ 2004-07-20 16:00 ` dave at hiauly1 dot hia dot nrc dot ca
  2004-07-20 16:04 ` pinskia at gcc dot gnu dot org
  4 siblings, 0 replies; 6+ messages in thread
From: dave at hiauly1 dot hia dot nrc dot ca @ 2004-07-20 16:00 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From dave at hiauly1 dot hia dot nrc dot ca  2004-07-20 16:00 -------
Subject: Re:  [3.5 regression] gcc.c-torture/execute/200

> ------- Additional Comments From pinskia at gcc dot gnu dot org  2004-07-20
> 15:44 -------
> Does this fail anymore?
> It seems like it does not:
> <http://gcc.gnu.org/ml/gcc-testresults/2004-07/msg00922.html>.

No.  Appears to have been fixed on July 9.

Dave


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16429


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

* [Bug regression/16429] [3.5 regression] gcc.c-torture/execute/20020412-1.c fails
  2004-07-08  1:44 [Bug regression/16429] New: [regression 3.5] New fails for gcc.c-torture/execute/20020412-1.c danglin at gcc dot gnu dot org
                   ` (3 preceding siblings ...)
  2004-07-20 16:00 ` dave at hiauly1 dot hia dot nrc dot ca
@ 2004-07-20 16:04 ` pinskia at gcc dot gnu dot org
  4 siblings, 0 replies; 6+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2004-07-20 16:04 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-07-20 16:04 -------
So closing as fixed.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16429


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

end of thread, other threads:[~2004-07-20 16:04 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-07-08  1:44 [Bug regression/16429] New: [regression 3.5] New fails for gcc.c-torture/execute/20020412-1.c danglin at gcc dot gnu dot org
2004-07-08  2:36 ` [Bug regression/16429] [3.5 regression] gcc.c-torture/execute/20020412-1.c fails pinskia at gcc dot gnu dot org
2004-07-08  2:50 ` dave at hiauly1 dot hia dot nrc dot ca
2004-07-20 15:44 ` pinskia at gcc dot gnu dot org
2004-07-20 16:00 ` dave at hiauly1 dot hia dot nrc dot ca
2004-07-20 16:04 ` pinskia at gcc dot gnu dot org

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