From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>,
kettenis@chello.nl, brobecker@gnat.com,
gdb-patches@sources.redhat.com
Subject: Re: [RFA] MIPS_TEXT symbols should be associated to .text section?
Date: Fri, 30 Jul 2004 13:37:00 -0000 [thread overview]
Message-ID: <410A4EF5.3080302@gnu.org> (raw)
In-Reply-To: <1438-Fri30Jul2004142656+0300-eliz@gnu.org>
>>Date: Fri, 30 Jul 2004 02:31:38 +0200
>>> From: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
>>>
>>
>>>> > Joel, I'm seeing similar problems on NetBSD/mips (NetBSD/pmax 1.6.2 to
>>>> > be precise).
>>
>>>
>>> AFAICS it will hit all elf{32-,32-n,64-}{big,little}mips targets (as
>>> opposed to *trad*mips), which are covered by SGI_COMPAT.
>
>
> Should we release a version of GDB that has so many platforms badly
> broken? Andrew?
The issue is fortunatly confined to MIPS. The announcement will make
that clear. We can then proceed with fixing it in mainline and either
backporting to 6.2.1 or moving on to 6.3.
Andrew
next prev parent reply other threads:[~2004-07-30 13:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-21 20:46 Joel Brobecker
2004-07-29 22:02 ` Joel Brobecker
2004-07-29 22:19 ` Thiemo Seufer
2004-07-29 23:15 ` Mark Kettenis
2004-07-30 0:31 ` Thiemo Seufer
2004-07-30 11:32 ` Eli Zaretskii
2004-07-30 13:37 ` Andrew Cagney [this message]
2004-07-30 18:04 ` Eli Zaretskii
2004-07-30 18:13 ` Joel Brobecker
2004-07-30 18:44 ` Eli Zaretskii
2004-07-30 18:55 ` Joel Brobecker
2004-07-30 19:36 ` Eli Zaretskii
2004-07-30 19:59 ` Andrew Cagney
2004-07-30 22:29 ` Michael Chastain
2004-07-30 18:08 ` Joel Brobecker
2004-07-30 18:57 ` Thiemo Seufer
2004-07-30 21:08 ` Mark Kettenis
2004-07-30 23:03 ` Joel Brobecker
2004-07-30 23:57 ` Thiemo Seufer
2004-07-30 18:19 ` Joel Brobecker
2004-07-30 0:17 ` Joel Brobecker
2004-07-22 15:47 David Anderson
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=410A4EF5.3080302@gnu.org \
--to=cagney@gnu.org \
--cc=brobecker@gnat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=kettenis@chello.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