From: Richard Earnshaw <rearnsha@arm.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Richard.Earnshaw@arm.com, gdb@sources.redhat.com
Subject: Re: ARM multi-arch NEWS
Date: Tue, 19 Feb 2002 09:33:00 -0000 [thread overview]
Message-ID: <200202191717.RAA27110@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Tue, 19 Feb 2002 12:01:17 EST." <3C7284DD.7080900@cygnus.com>
> > Richard,
> >>
> >> Can I suggest adding an entry to the NEWS file mentioning that the Arm
> >> is now multi-arch?
> >>
> >> enjoy,
> >> Andrew
> >>
> >
> >
> > Well, so far only one target is genuinely multi-arch. The rest (including
> > generic) are still not quite there ;-(
>
> I think just getting to the point of throwing the multi-arch switch
> (level 1) is newsworthy achievement :-) (It also serves as a heads up
> to Arm developers - many of the big V little bugs just mysteriously
> disappeared :-)).
>
> enjoy,
> Andrew
>
Hmm, something like this then?
diff -p -r1.56 NEWS
*** NEWS 2002/02/10 17:34:05 1.56
--- NEWS 2002/02/19 17:14:50
*************** it will be treated as a corefile. If it
*** 36,43 ****
--- 36,49 ----
GDB will attempt to attach it as a process, and if no such process
is found, will then attempt to open it as a corefile.
+ * Changes in ARM configurations.
+
+ Multi-arch support is enabled for all ARM configurations. The ARM/NetBSD
+ configuration is fully multi-arch.
+
* New native configurations
+ ARM NetBSD arm*-*-netbsd*
x86 OpenBSD i[3456]86-*-openbsd*
AMD x86-64 running GNU/Linux x86_64-*-linux-*
next prev parent reply other threads:[~2002-02-19 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 8:46 Andrew Cagney
2002-02-19 8:49 ` Richard Earnshaw
2002-02-19 9:01 ` Andrew Cagney
2002-02-19 9:33 ` Richard Earnshaw [this message]
2002-02-19 13:09 ` Andrew Cagney
2002-02-20 2:50 ` Richard Earnshaw
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=200202191717.RAA27110@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=ac131313@cygnus.com \
--cc=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