From: jlarmour@redhat.com (Jonathan Larmour)
To: mark@codesourcery.com
Cc: gcc@gcc.gnu.org
Subject: Re: Branching for GCC 3.0
Date: Mon, 08 Jan 2001 07:57:00 -0000 [thread overview]
Message-ID: <200101081556.f08FueV16619@murgh.cambridge.redhat.com> (raw)
In-Reply-To: <20010107125803Q.mitchell@codesourcery.com>
In article < 20010107125803Q.mitchell@codesourcery.com > you write:
>
>Richard's patch to support -shared-libgcc was the last functional item
>on my list of things to do before GCC 3.0.
If gcc is branched now, does this mean that the libgcc ABI is now set
in stone?
I am specifically wondering because I wanted to investigate tidying up
the "gthread" API, but I hadn't had time - but I was very specifically
going to be given time soon (not before next week :-)).
My concern is that if I don't get it in in time for this branch it can
never ever happen... And similarly with any other future changes that
may ever change the libgcc ABI.
Or are my worries about the ABI unnecessary?
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Un cheval, pas du glue. Pas du cheval, beaucoup du glue. || Opinions==mine
next prev parent reply other threads:[~2001-01-08 7:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-07 12:51 Mark Mitchell
2001-01-07 13:40 ` Joseph S. Myers
2001-01-08 4:44 ` Gabriel Dos Reis
2001-01-08 9:00 ` Phil Edwards
2001-01-09 11:37 ` Mark Mitchell
2001-01-09 23:17 ` Martin Kahlert
2001-01-09 23:27 ` Mark Mitchell
2001-01-10 8:59 ` Alexandre Petit-Bianco
2001-01-10 2:03 ` Nathan Sidwell
2001-01-08 7:57 ` Jonathan Larmour [this message]
2001-01-08 9:27 ` Joe Buck
2001-01-08 9:34 ` Jonathan Larmour
[not found] ` <mailpost.978974918.744@postal.sibyte.com>
2001-01-08 15:45 ` Chris G. Demetriou
2001-01-08 10:27 ` Joseph S. Myers
2001-01-08 14:45 ` Marc Espie
2001-01-08 15:07 ` Mark Mitchell
2001-01-07 14:31 Brad Lucier
2001-01-07 14:40 ` Mark Mitchell
2001-01-07 14:44 ` Brad Lucier
2001-01-07 14:52 ` Mark Mitchell
2001-01-08 7:43 ` Jeffrey A Law
2001-01-08 8:12 ` Robert Lipe
2001-01-08 8:46 ` Franz Sirl
2001-01-08 8:52 ` Jeffrey A Law
2001-01-08 9:07 ` Franz Sirl
2001-01-08 9:26 ` Jakub Jelinek
2001-01-07 17:28 ` Geoff Keating
2001-01-07 17:48 ` David Edelsohn
2001-01-07 17:58 ` Brad Lucier
2001-01-07 15:43 dewar
2001-01-07 18:08 dewar
2001-01-08 9:42 ` Geoff Keating
2001-01-08 8:48 Brad Lucier
2001-01-08 14:50 Mike Stump
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=200101081556.f08FueV16619@murgh.cambridge.redhat.com \
--to=jlarmour@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).