From: Corinna Vinschen <gdb@sources.redhat.com>
To: gdb@sources.redhat.com
Subject: Re: Where to set correct value for tdep->struct_return for Cygwin?
Date: Thu, 20 Mar 2003 15:39:00 -0000 [thread overview]
Message-ID: <20030320153930.GZ21269@cygbert.vinschen.de> (raw)
In-Reply-To: <3E79DDFB.4030003@redhat.com>
On Thu, Mar 20, 2003 at 10:27:55AM -0500, Andrew Cagney wrote:
> >Hi,
> >
> >I just found the following problem:
> >
> >In i386-tdep.c::i386_gdbarch_init(), tdep->struct_return is set to
> >pcc_struct_return by default. Several i386 targets set this value
> >in their appropriate _init function to reg_struct_return (e. g. the
> >bsd and interix targets).
> >
> >Cygwin is using reg_struct_return as well but unfortunately in contrast
> >to Interix it has no own tdep.c file and so there's no appropriate _init
> >function as e. g. i386_interix_init_abi() available to set that value.
> >This results in having tdep->struct_return still set to pcc_struct_return
> >and about 25 fails in the testsuite.
> >
> >So the question is, where to set that value? Shall we add a new
> >cygwin-tdep.c
> >file, just to set this one value? Or is there some already existing
> >obvious
> >place to do this? win32-nat.c seems to be not a good chice, btw.
>
> If both interix and cygwin are sharing a common ABI, then shouldn't that
> common ABI code live in i386-win32-tdep.c?
I didn't say Interix and Cygwin share a common ABI. It's just this
one the same. Interix adds some additional stuff which isn't the
same for Cygwin.
Corinna
--
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:vinschen@redhat.com
next prev parent reply other threads:[~2003-03-20 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 15:20 Corinna Vinschen
2003-03-20 15:27 ` Andrew Cagney
2003-03-20 15:39 ` Corinna Vinschen [this message]
2003-03-20 16:55 ` Andrew Cagney
2003-03-21 5:00 ` Eli Zaretskii
2003-10-09 21:32 ` Michael Snyder
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=20030320153930.GZ21269@cygbert.vinschen.de \
--to=gdb@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