From: Andrew Cagney <ac131313@cygnus.com>
To: Mark Kettenis <kettenis@wins.uva.nl>
Cc: gdb@sources.redhat.com
Subject: Re: current CVS gdb and SSE xmm registers don't work [RESEND]
Date: Thu, 02 Aug 2001 10:11:00 -0000 [thread overview]
Message-ID: <3B6989B0.2030007@cygnus.com> (raw)
In-Reply-To: <200108021000.f72A0IZ03115@delius.kettenis.local>
> Date: Wed, 01 Aug 2001 19:19:01 -0400
> From: Andrew Cagney <ac131313@cygnus.com>
>
>> Fixing this requires a serious amount of work. It requires changes to
> > both GDB and glibc. It definitely isn't going to happen overnight,
> > especially since I only have a Pentium MMX machine.
>
> Mark, it would proably be useful to mention this in gdb/README under the
> host/target section.
>
> Which section do you mean? We only have a section `Host/target
> specific installation notes'. Doesn't seem an appropriate section to
> me. Should I add a section `Known problems' for this purpose (just
> before or after `Reporting Bugs')?
If I changed the title to ``Host/target specific notes'' would it help?
I would like it to be possible for a user to just read (dare I say skim?
:-) the README file and then successfully build GDB. Having all the
host/target specific issues in one spot would hopefully help this.
Andrew
next prev parent reply other threads:[~2001-08-02 10:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <01073123414300.04519@astral>
[not found] ` <s3ibslzjsy4.fsf@soliton.wins.uva.nl>
[not found] ` <3B688E65.1040308@cygnus.com>
2001-08-02 3:00 ` Mark Kettenis
2001-08-02 7:02 ` Eli Zaretskii
2001-08-02 10:12 ` Andrew Cagney
2001-08-02 12:00 ` [PATCH] Re: current CVS gdb and SSE xmm registers don't work Mark Kettenis
2001-08-02 10:11 ` Andrew Cagney [this message]
2001-08-02 12:06 ` current CVS gdb and SSE xmm registers don't work [RESEND] Mark Kettenis
2001-08-03 1:49 ` 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=3B6989B0.2030007@cygnus.com \
--to=ac131313@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