From: Zack Weinberg <zack@codesourcery.com>
To: Geoff Keating <geoffk@geoffk.org>
Cc: gcc@gcc.gnu.org
Subject: Re: b-i-b status on Darwin
Date: Sat, 14 Dec 2002 00:23:00 -0000 [thread overview]
Message-ID: <87wumd6o7j.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <200212140609.gBE69IG00642@desire.geoffk.org> (Geoff Keating's message of "Fri, 13 Dec 2002 22:09:18 -0800")
Geoff Keating <geoffk@geoffk.org> writes:
> To help Zack out (or at least to make sure that the tree doesn't
> suddenly break on Darwin), I tried bootstrapping the b-i-b on Darwin.
>
> The first problem I hit appears to be a merge problem,
> unwind-dw2-fde-darwin.c doesn't exist on the branch. I worked around
> it by copying the mainline version. Zack, can you check that no other
> files are missing and that no patches got lost? I'm most worried
> about losing testcases.
I don't know how this happened. I generated recursive directory
listings in my 3.3 and 3.4 trees and compared them, this is what I got:
files that should be added to 3.4 -- corrected in my working copy:
gcc/ChangeLog.7
gcc/unwind-dw2-fde-darwin.c
files that were deliberately removed from 3.4:
gcc/config/alpha/vxworks.h
gcc/config/arm/vxarm.h
gcc/config/i386/vxi386.h
gcc/config/i960/t-vxworks960
gcc/config/i960/vx960-coff.h
gcc/config/i960/vx960.h
gcc/config/m68k/t-vxworks68
gcc/config/m68k/vxm68k.h
gcc/config/mips/vxworks.h
gcc/config/rs6000/vxppc.h
gcc/config/sparc/t-vxsparc
gcc/config/sparc/t-vxsparc64
gcc/config/sparc/vxsim.h
gcc/config/sparc/vxsparc64.h
gcc/config/sparc/vxsparc.h
gcc/config/vax/vms.h
gcc/config/vax/xm-vms.h
files only in 3.4 -- I believe all of these are new on the branch, not
removed on the trunk and the deletion didn't propagate:
config/accross.m4
contrib/gthr_supp_vxw_5x.c
gcc/config/rs6000/t-vxworks
gcc/config/rs6000/vxworks.h
gcc/config/sh/libgcc-glibc.ver
gcc/config/t-libunwind
gcc/config/t-vxworks
gcc/config/vxlib.c
gcc/config/vxworks.h
gcc/coretypes.h
gcc/cp/cxxfilt.c
gcc/gcov-dump.c
gcc/gcov-iov.c
gcc/testsuite/gcc.c-torture/execute/shiftopt-1.c
gcc/testsuite/gcc.dg/bf-ms-layout.c
gcc/testsuite/gcc.dg/bf-no-ms-layout.c
gcc/testsuite/gcc.dg/builtins-2.c
gcc/testsuite/gcc.dg/builtins-3.c
gcc/testsuite/gcc.dg/i386-cmov1.c
gcc/testsuite/gcc.dg/i386-cmov2.c
gcc/testsuite/gcc.dg/i386-cmov3.c
gcc/testsuite/gcc.dg/i386-ssefp-1.c
gcc/testsuite/gcc.dg/i386-ssefp-2.c
gcc/testsuite/gcc.dg/sibcall-5.c
gcc/testsuite/gcc.dg/sibcall-6.c
gcc/testsuite/g++.dg/inherit/covariant2.C
gcc/testsuite/g++.dg/inherit/covariant3.C
gcc/testsuite/g++.dg/inherit/covariant4.C
gcc/unwind-libunwind.c
See my next message for the merge plan.
zw
next prev parent reply other threads:[~2002-12-14 7:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 23:42 Geoff Keating
2002-12-14 0:09 ` Daniel Berlin
2002-12-14 0:23 ` Zack Weinberg [this message]
2002-12-14 1:42 ` Geoff Keating
2002-12-14 7:44 ` Andreas Tobler
2002-12-14 13:46 ` Geoff Keating
2002-12-16 15:45 ` Mike Stump
2002-12-14 10:57 ` David Edelsohn
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=87wumd6o7j.fsf@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@geoffk.org \
/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).