From: Andrew Cagney <ac131313@redhat.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: fnf@ninemoons.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Outwit compiler dead code elimination in break.exp test (revised patch)
Date: Mon, 08 Dec 2003 23:49:00 -0000 [thread overview]
Message-ID: <3FD50DEA.2070203@redhat.com> (raw)
In-Reply-To: <20031208042046.EF94D4B412@berman.michael-chastain.com>
> ---
>
> break.c and break1.c need copyright notices.
> Andrew C can provide a list of years for break.c,
> covering the time before it was moved to sourceware.
Fred, in case you're wondering, one of the Red Hat chores is to, on
demand, track down the pre-history of files with no copyright status.
The history:
gdb/testsuite/gdb.base/break.c:
date: 2003/11/13 15:34:39; author: ezannoni; state: Exp; lines: +14 -14
date: 2002/01/07 19:21:26; author: law; state: Exp; lines: +52 -2
date: 1999/04/16 01:34:30; author: shebs; state: Exp;
The "pre-history":
gdb/testsuite/gdb.base/break.c:
date: 1999/10/02 00:24:35; author: kevinb; state: Exp; lines: +2 -1
date: 1999/09/08 18:18:56; author: shebs; state: Exp; lines: +1 -1
date: 1999/06/25 23:44:28; author: shebs; state: Exp; lines: +19 -0
date: 1995/04/17 19:55:19; author: kingdon; state: Exp; lines: +2 -2
date: 1995/03/24 22:06:03; author: kung; state: Exp; lines: +4 -0
date: 1995/03/16 00:06:48; author: grossman; state: Exp; lines: +3 -3
date: 1994/06/07 01:56:04; author: shebs; state: Exp;
gdb/testsuite/gdb.t06/gdbme.c (yep!):
date: 1994/06/07 22:51:18; author: shebs; state: dead; lines: +0 -0
date: 1993/02/25 18:51:37; author: ian; state: Exp;
gdb/testsuite/gdb.t06/in-gdb.c (I kid you not!):
date: 1993/02/25 18:51:38; author: ian; state: dead; lines: +0 -0
date: 1993/02/21 20:01:14; author: mtw; state: Exp;
* gdb/testsuite: Initial creation of gdb/testsuite.
Migrated dejagnu testcases and support files for testing nm to
gdb/testsuite from deja-gnu. These files were moved "as is"
with no modifications. This migration is part of a major overhaul
of dejagnu. The modifications to these testcases, etc., which
will allow them to work with the new version of dejagnu will be
made in a future update.
deja-gnu/deja-gnu/gdb.t06/in-gdbme.c (I kid you not!):
date: 1993/10/14 00:10:57; author: rich; state: dead; lines: +0 -0
date: 1992/11/04 22:31:42; author: ian; state: Exp; lines: +13 -0
date: 1992/10/23 18:57:46; author: ian; state: Exp; lines: +18 -4
date: 1992/08/09 05:03:10; author: rob; state: Exp; lines: +6 -1
date: 1992/07/18 03:22:58; author: rob; state: Exp;
So not a bad list of copyright years!
Andrew
PS: In case no one believes me, this is the original code:
#include <stdio.h>
/*
* The following functions do nothing useful. They are included simply
* as places to try setting breakpoints at. They are explicitly
* "one-line functions" to verify that this case works (some versions
* of gcc have or have had problems with this).
*/
int marker1 () { return (0); }
int marker2 (a) int a; { return (1); }
void marker3 (a, b) char *a, *b; {}
void marker4 (d) long d; {}
/*
* This simple classical example of recursion is useful for
* testing stack backtraces and such.
*/
main (argc, argv, envp)
int argc;
char *argv[], **envp;
{
if (argc != 2) {
fprintf (stderr, "usage: factorial <number>\n");
exit (1);
} else {
printf ("%d\n", factorial (atoi (argv[1])));
}
marker1 ();
marker2 (43);
marker3 ("stack", "trace");
marker4 (177601976L);
exit (0);
}
int factorial (value)
int value;
{
if (value > 1) {
value *= factorial (value - 1);
}
return (value);
}
next prev parent reply other threads:[~2003-12-08 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 4:20 Michael Elizabeth Chastain
2003-12-08 23:49 ` Andrew Cagney [this message]
2003-12-09 5:06 ` [PATCH] Outwit compiler dead code elimination in break.exp test Fred Fish
-- strict thread matches above, loose matches on Subject: below --
2003-11-29 23:05 Fred Fish
2003-12-01 17:52 ` Andrew Cagney
2003-12-07 21:21 ` [PATCH] Outwit compiler dead code elimination in break.exp test (revised patch) Fred Fish
2003-12-08 0:31 ` Andrew Cagney
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=3FD50DEA.2070203@redhat.com \
--to=ac131313@redhat.com \
--cc=fnf@ninemoons.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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