From: Andrew Cagney <ac131313@cygnus.com>
To: Denis Joseph Barrow <DJBARROW@de.ibm.com>
Cc: gdb-patches@sourceware.cygnus.com, s390-patches@gnu.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: New gdb 31 & 64 bit patches for S/390
Date: Thu, 05 Jul 2001 12:46:00 -0000 [thread overview]
Message-ID: <3B44C429.8090007@cygnus.com> (raw)
In-Reply-To: <OF774BA4B4.AF34F794-ONC1256A80.005F1614@de.ibm.com>
> There are some target specific structures for to find out if I'm in a
> signal handler which I
> currently need see the s390_offsetof stuff in the tm-s390.c.
>
> What about using the __attribute__(packed) gcc extension.
> & add a
> #ifndef gcc
> define __attribute__
> #endif
No. So far GDB has managed to avoid a dependency on GCCoteric features,
I don't see any reason to change this.
With regard to the other target specific structures, I suggested moving
them to s390-nat.c since (I think) only that file would be using them
(?correct). s390-nat.c is very host=target specific - it needs to
correctly unpack the data returned from ptrace/procfs. However, even
there, the __attribute__(packed) should be removed.
> for non gcc compilers this would get around some of the common problems,
> the only other way is for me to
> add #defines for all the offsets I need.
Remember s390-tdep.c analizes and implements an ABI. That ABI is
hopefully publised and defined. It isn't going to change. If it does
then the debugger, the compiler and who knows what else will need to be
modified.
Because the ABI is ``set in stone'' constants using enums (not #defines)
are typically used in the *-tdep.c file.
For what its worth, BFD has adopted the strategy of:
o having the ABI constants wired in
o when host=target=s390-linux,
verify that those constants havn't
been changed by someones foobar.
Andrew
next prev parent reply other threads:[~2001-07-05 12:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-05 10:24 Denis Joseph Barrow
2001-07-05 12:46 ` Andrew Cagney [this message]
2001-07-08 0:53 ` Eli Zaretskii
2001-07-08 19:23 ` Andrew Cagney
[not found] <OFEFF0AD94.761C34C1-ONC1256AB6.005503EE@de.ibm.com>
2001-08-28 16:33 ` Daniel Jacobowitz
2001-09-05 21:45 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2001-08-15 2:22 Denis Joseph Barrow
2001-08-15 9:03 ` Andrew Cagney
2001-08-15 9:54 ` Andrew Cagney
2001-08-13 9:47 Denis Joseph Barrow
2001-08-13 3:06 Denis Joseph Barrow
2001-08-13 9:31 ` Andrew Cagney
2001-07-06 2:31 Denis Joseph Barrow
2001-07-05 9:19 Denis Joseph Barrow
2001-07-05 12:36 ` Andrew Cagney
2001-07-05 9:15 Denis Joseph Barrow
2001-07-05 5:04 Denis Joseph Barrow
2001-07-05 3:57 Denis Joseph Barrow
2001-07-05 10:11 ` Andrew Cagney
2001-07-05 10:11 ` Andrew Cagney
2001-07-05 3:12 Denis Joseph Barrow
2001-06-18 3:32 DJBARROW
[not found] <C1256A02.00573066.00@d12mta09.de.ibm.com>
2001-03-01 10:39 ` Nick Clifton
2001-03-01 2:50 DJBARROW
2001-03-01 10:37 ` Nick Clifton
2001-02-27 12:39 DJBARROW
2001-02-28 16:13 ` Nick Clifton
2001-06-15 9:53 ` Andrew Cagney
2001-06-15 11:46 ` Andreas Jaeger
2001-06-15 12:22 ` Andrew Cagney
2001-07-04 11:25 ` Andrew Cagney
2001-07-04 21:02 ` Andrew Cagney
2001-07-04 21:02 ` Andrew Cagney
2001-07-04 21:02 ` 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=3B44C429.8090007@cygnus.com \
--to=ac131313@cygnus.com \
--cc=DJBARROW@de.ibm.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=s390-patches@gnu.org \
--cc=schwidefsky@de.ibm.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