From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Mark Kettenis <kettenis@wins.uva.nl>
Cc: gdb@sources.redhat.com
Subject: Re: V3 ABI stuff is broken
Date: Fri, 01 Jun 2001 20:56:00 -0000 [thread overview]
Message-ID: <np66eflejp.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <200105242031.f4OKVUO07451@delius.kettenis.local>
I think I've fixed this ("PATCH: relax restrictions on
per-architecture data registration"). If this problem isn't gone,
please post.
Mark Kettenis <kettenis@wins.uva.nl> writes:
> The new V3 ABI code in gnu-v3-abi.c uses a per-architecture
> data-pointer, but it looks like this mechanism is broken, at least for
> targets that are not yet multi-arch.
>
> If I understand things correcly in that case startup_gdbarch is used.
> However, the per-architecture data-pointer isn't allocated/initialized
> for startup_gdbarch. This leads to a lot of test failures for
> alpha-unknown-freebsd5.0 when using GCC 3.0.
>
> Should arch-utils.c:initialize_current_architecture() always call
> gdbarch_update_p(), even if the target is not multi-arch?
next prev parent reply other threads:[~2001-06-01 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 13:31 Mark Kettenis
2001-06-01 20:56 ` Jim Blandy [this message]
2001-06-03 3:04 ` Mark Kettenis
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=np66eflejp.fsf@zwingli.cygnus.com \
--to=jimb@zwingli.cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@wins.uva.nl \
/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