From: Joseph Myers <joseph@codesourcery.com>
To: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
Cc: "Michael Matz" <matz@suse.de>, "Martin Liška" <mliska@suse.cz>,
"GCC Development" <gcc@gcc.gnu.org>
Subject: Re: [RFC] Adding Python as a possible language and it's usage
Date: Mon, 30 Jul 2018 14:51:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1807301428510.17805@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAJA7tRa72pCwjy1f7k5LK4dkC8MLjm_JZCrWhQvzbzG02m6XbA@mail.gmail.com>
On Sat, 28 Jul 2018, Ramana Radhakrishnan wrote:
> > Obviously if you're bootstrapping core packages and their build
> > dependencies, use in glibc is more or less equivalent to use in GCC. (But
> > if build dependencies include those involved in testing, you already have
> > python as one for glibc, and Tcl for GCC, for example.)
>
> This implies that the decision for glibc has been made. while you
> imply above that the discussion is still on going ?
Python has been used for some glibc tests for some time. It's usage to
replace other Perl and Awk scripts (and especially those required for the
build) for which there is discussion - though as no-one has objected to
such a change we may effectively have consensus.
https://sourceware.org/ml/libc-alpha/2018-07/msg00559.html
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-07-30 14:34 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 12:49 Martin Liška
2018-07-18 1:01 ` David Malcolm
2018-07-19 20:24 ` Karsten Merker
2018-07-20 10:02 ` Matthias Klose
2018-07-20 10:07 ` Martin Liška
2018-07-18 9:51 ` Richard Biener
2018-07-18 10:03 ` Richard Earnshaw (lists)
2018-07-18 10:56 ` David Malcolm
2018-07-18 11:08 ` Jakub Jelinek
2018-07-18 11:31 ` Jonathan Wakely
2018-07-18 12:06 ` Eric S. Raymond
2018-07-18 12:15 ` Jonathan Wakely
2018-07-18 12:50 ` Joel Sherrill
2018-07-18 14:29 ` Matthias Klose
2018-07-18 14:46 ` Janne Blomqvist
2018-07-20 10:01 ` Martin Liška
2018-07-20 16:54 ` Segher Boessenkool
2018-07-20 17:12 ` Paul Koning
2018-07-20 17:59 ` Segher Boessenkool
2018-07-20 18:59 ` Konovalov, Vadim
2018-07-20 20:09 ` Matthias Klose
2018-07-20 20:15 ` Konovalov, Vadim
2018-07-18 21:28 ` Eric S. Raymond
2018-07-23 14:31 ` Joseph Myers
2018-07-18 22:42 ` Segher Boessenkool
2018-07-19 12:28 ` Florian Weimer
2018-07-19 20:08 ` Richard Earnshaw (lists)
2018-07-20 9:49 ` Michael Clark
2018-07-19 15:56 ` Jeff Law
2018-07-19 16:12 ` Eric Gallager
2018-07-20 10:05 ` Martin Liška
2018-07-18 15:13 ` Boris Kolpackov
2018-07-18 16:56 ` Paul Koning
2018-07-18 17:29 ` Boris Kolpackov
2018-07-18 17:44 ` Paul Koning
2018-07-18 18:11 ` Matthias Klose
2018-07-20 11:04 ` Martin Liška
2018-07-19 14:47 ` Konovalov, Vadim
2018-07-23 14:21 ` Joseph Myers
2018-07-27 14:31 ` Michael Matz
2018-07-27 14:38 ` Michael Matz
2018-07-28 3:01 ` Matthias Klose
2018-07-27 14:54 ` Joseph Myers
2018-07-27 15:11 ` Michael Matz
2018-07-28 0:26 ` Paul Smith
2018-07-30 14:34 ` Joseph Myers
2018-07-28 12:11 ` Ramana Radhakrishnan
2018-07-28 17:23 ` David Malcolm
2018-07-30 14:51 ` Joseph Myers [this message]
2018-07-30 16:29 ` Andreas Schwab
2018-07-28 2:29 ` konsolebox
[not found] <1531832440.64499.ezmlm@gcc.gnu.org>
2018-07-17 17:13 ` Basile Starynkevitch
2018-07-17 23:52 ` David Malcolm
2018-07-17 20:37 David Niklas
2018-07-18 0:23 ` David Malcolm
2018-07-18 0:38 ` Paul Koning
2018-07-18 16:41 ` doark
2018-07-18 17:22 ` doark
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=alpine.DEB.2.20.1807301428510.17805@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=matz@suse.de \
--cc=mliska@suse.cz \
--cc=ramana.gcc@googlemail.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).