From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Type cleanups
Date: Mon, 13 May 2002 06:59:00 -0000 [thread overview]
Message-ID: <20020513135950.GB19484@nevyn.them.org> (raw)
In-Reply-To: <3CDF3081.1020900@cygnus.com>
On Sun, May 12, 2002 at 11:18:25PM -0400, Andrew Cagney wrote:
> >In order to fix gdb/277, I needed to move a lot of members of 'struct
> >type'. This patch flushes out all (that I could find) direct accesses of
> >these
> >members instead of through the proper macros. It's possible that I missed
> >some; if so, the next patch will cause whichever files I missed to stop
> >compiling. I'm pretty sure I got them all, though. I also clean up the
> >only remaining references to 'sizeof (struct type)': dstread.c had a clone
> >of alloc_type, and hpread.c needed to call replace_type like the other
> >readers.
> >
> >This patch should have no effect. On i386-linux, I get byte-for-byte
> >identical GDB binaries (all 5591185 bytes of it, debugging information
> >and all; no -g3 here).
> >
> >OK to commit?
>
> Did you check all the cross targets build per MAINTAINERS? From memory
> sh-hms[bfd] and avr[need to look] don't build at present (well as of
> ~2002-05-12-gmt).
>
> If that has been checked, then yes ``obviously''.
A few don't build; none of them are my fault. For the record:
At least fr30-elf, mn10300-elf, and v850-elf have missing
dependencies off in sim/ land; they built with non-parallel make only.
hppa1.1-hp-proelf wants dl.h and machine/save_state.h in
hppa-tdep.c, and was already marked broken. The nice gawk segment
doesn't notice that...
Several targets (i586-pc-msdosdjgpp, sparc-elf, sparc64-elf)
failed with this message (also JB_SP for Sparc):
In file included from /usr/include/setjmp.h:30,
from ../../src-build/gdb/top.c:58:
/usr/include/bits/setjmp.h:31: warning: `JB_PC' redefined
tm.h:57: warning: this is the location of the previous definition
make[1]: *** [top.o] Error 1
sh-hms failed with a reference to some new SHmedia code.
x86-64 failed with:
libgdb.a(solib.o): In function `clear_solib':
/opt/src/gdb/crossbuild/obj.x86_64-linux-gnu/gdb/../../src-build/gdb/solib.c:742:
undefined reference to `disable_breakpoints_in_shlibs'
libgdb.a(solib-svr4.o): In function `enable_break':
/opt/src/gdb/crossbuild/obj.x86_64-linux-gnu/gdb/../../src-build/gdb/solib-svr4.c:856:
undefined reference to `remove_solib_event_breakpoints'
/opt/src/gdb/crossbuild/obj.x86_64-linux-gnu/gdb/../../src-build/gdb/solib-svr4.c:983:
undefined reference to `create_solib_event_breakpoint'
Is x86-64 really "maintenance only"?
Anyway, committed.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-05-13 13:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-12 17:34 Daniel Jacobowitz
2002-05-12 20:18 ` Andrew Cagney
2002-05-12 20:40 ` Daniel Jacobowitz
2002-05-12 21:31 ` Andrew Cagney
2002-05-13 11:46 ` Daniel Jacobowitz
2002-05-13 12:54 ` Daniel Berlin
2002-05-13 12:57 ` Daniel Jacobowitz
2002-05-13 6:59 ` Daniel Jacobowitz [this message]
2002-05-13 8:37 ` Andrew Cagney
2002-05-13 8:51 ` Elena Zannoni
2002-05-13 9:11 ` Andrew Cagney
2002-05-13 9:19 ` Elena Zannoni
2002-05-13 11:50 ` Daniel Jacobowitz
2002-05-13 11:59 ` Daniel Jacobowitz
2002-05-13 15:14 ` Andrew Cagney
2002-05-13 16:09 ` Daniel Jacobowitz
2002-05-13 18:37 ` Elena Zannoni
2002-05-14 17:09 ` Andrew Cagney
2002-05-17 1:11 ` Eli Zaretskii
2002-05-17 8:02 ` Daniel Jacobowitz
2002-05-17 9:14 ` Eli Zaretskii
2002-05-17 10:21 ` Daniel Jacobowitz
2002-05-17 10:34 ` Andrew Cagney
2002-05-18 0:15 ` Eli Zaretskii
2002-05-18 0:13 ` Eli Zaretskii
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=20020513135950.GB19484@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.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