From: Eric Christopher <echristo@redhat.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: Michael Snyder <msnyder@redhat.com>,
Daniel Jacobowitz <drow@mvista.com>,
gdb-patches@sources.redhat.com, cagney@redhat.com,
kevinb@redhat.com
Subject: Re: [RFC] Mips, N32, cc, gcc, and gdb (longish)
Date: Fri, 02 Aug 2002 12:52:00 -0000 [thread overview]
Message-ID: <1028317855.1794.2.camel@ghostwheel.cygnus.com> (raw)
In-Reply-To: <3D4ABFEF.50807@ges.redhat.com>
> I hope it wasn't me :-)
>
> GCC need to be fixed. Either they need to define a new abi that
> specifies all their breakage OR they fix it to match the offical abi. I
> have a sinking feeling that they'll do both.
>
It is an interesting issue then isn't it? Break ABI compatability or
define another one...
-eric
--
I don't want a pony, I want a rocket
powered jetpack!
prev parent reply other threads:[~2002-08-02 19:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 18:32 Michael Snyder
2002-08-01 18:57 ` Daniel Jacobowitz
2002-08-01 19:42 ` Michael Snyder
2002-08-01 19:45 ` Daniel Jacobowitz
2002-08-01 20:19 ` Michael Snyder
2002-08-02 10:22 ` Andrew Cagney
2002-08-02 12:52 ` Eric Christopher [this message]
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=1028317855.1794.2.camel@ghostwheel.cygnus.com \
--to=echristo@redhat.com \
--cc=ac131313@ges.redhat.com \
--cc=cagney@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@redhat.com \
--cc=msnyder@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