public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: dnovillo@redhat.com, Jason Molenda <jason@molenda.com>
Cc: gcc@gcc.gnu.org
Subject: tree-ssa-cvs corrupt
Date: Fri, 03 Jan 2003 16:06:00 -0000	[thread overview]
Message-ID: <u81y3uqkuf.fsf@gromit.moeb> (raw)


Jason,

it seems that your latest patch to the tree-ssa branch has corrupted
the testsuite.

I got lots of failures in the testsuite due to missing first characters.

Note the missing "/" at the beginning of the line:
arthur:/cvs/gcc-tree-ssa-20020619-branch/gcc/testsuite/gcc.c-torture/compile:[0]
$ head 20001226-1.c
* This testcase exposed two branch shortening bugs on powerpc.  */

$ cvs status 20001226-1.c
===================================================================
File: 20001226-1.c      Status: Up-to-date

   Working revision:    1.1.26.1
   Repository revision: 1.1.26.1        /cvs/cvs-mirror-rsync/gcc/gcc/gcc/testsuite/gcc.c-torture/compile/20001226-1.c,v
   Sticky Tag:          tree-ssa-20020619-branch (branch: 1.1.26)
   Sticky Date:         (none)
   Sticky Options:      (none)

$ cvs diff -D yesterday  20001226-1.c 
Index: 20001226-1.c
===================================================================
RCS file: /cvs/cvs-mirror-rsync/gcc/gcc/gcc/testsuite/gcc.c-torture/compile/20001226-1.c,v
retrieving revision 1.1
retrieving revision 1.1.26.1
diff -u -p -r1.1 -r1.1.26.1
--- 20001226-1.c        27 Dec 2000 11:01:03 -0000      1.1
+++ 20001226-1.c        25 Nov 2002 04:25:27 -0000      1.1.26.1
@@ -1,4 +1,4 @@
-/* This testcase exposed two branch shortening bugs on powerpc.  */
+* This testcase exposed two branch shortening bugs on powerpc.  */
 
 #define C(a,b) \
   if (a > b)  goto gt; \

Jason, can you check your latest commit again, please?
Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

             reply	other threads:[~2003-01-03 16:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03 16:06 Andreas Jaeger [this message]
2003-01-03 16:29 ` Diego Novillo
2003-01-03 16:34   ` Diego Novillo
2003-01-03 16:58   ` Andreas Jaeger
2003-01-03 20:55   ` Mike Stump
2003-01-04  0:35   ` Phil Edwards
2003-01-05  7:46     ` Zack Weinberg
2003-01-05 21:06       ` Diego Novillo
2003-01-05 21:33         ` Neil Booth
2003-01-05 23:07           ` Zack Weinberg
2003-01-05 23:07             ` Neil Booth
2003-01-05 23:18               ` Zack Weinberg
2003-01-05 23:37                 ` Neil Booth
2003-01-06  0:27                   ` Zack Weinberg
2003-01-06  1:06                 ` Gabriel Dos Reis
2003-01-06 22:57                 ` Geoff Keating
2003-01-06 23:20                   ` Neil Booth
2003-01-07  1:33   ` Richard Henderson
2003-01-07  1:34     ` Richard Henderson
2003-01-07  2:34     ` Diego Novillo
2003-01-03 16:22 Jason Merrill
2003-01-05 22:14 Bonzini
2003-01-05 22:53 ` Neil Booth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=u81y3uqkuf.fsf@gromit.moeb \
    --to=aj@suse.de \
    --cc=dnovillo@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jason@molenda.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).