From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Aaron Gray <aaronngray.lists@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: Wanted: original ConceptGCC downloads / branch, concepts-lite branch
Date: Wed, 17 Aug 2022 14:55:47 +0200 [thread overview]
Message-ID: <CAH6eHdSLzKGXbByEPTzT3t=f_MjVJNzA_RQphvvJnTpnOuV+iA@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdTbOYhcr3GQhHvUu5Qa8PzwSQtJOnMe62Qhesk4iTEmww@mail.gmail.com>
On Wed, 17 Aug 2022, 14:46 Jonathan Wakely, <jwakely.gcc@gmail.com> wrote:
>
>
> On Wed, 17 Aug 2022, 13:43 Aaron Gray via Gcc, <gcc@gcc.gnu.org> wrote:
>
>> Hi,
>>
>> I am looking for the original ConceptGCC source code, the
>> https://www.generic-programming.org/software/ConceptGCC/download.html has
>> all broken links and the SVN is gone.
>>
>> Is this available on GCC git or SVN ?
>>
>
> I don't think so, but I can't check now. I would ask Doug Gregor where
> that code can be found now.
>
>
>> Also I am wondering if the original concepts-lite code is available too
>> anywhere please ?
>>
>
> Define "original". Andrew Sutton's Concepts Lite implementation was merged
> into GCC trunk, and evolved to also support C++20 concepts.
>
I think it was merged in August 2015 and first released in GCC 6.1
>
>
>> Also any pointers to the documentation for the current implementation ?
>>
>
> Only comments in the code, I think.
>
>
>
next prev parent reply other threads:[~2022-08-17 12:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 11:42 Aaron Gray
2022-08-17 12:16 ` Ben Boeckel
2022-08-17 12:29 ` Aaron Gray
2022-08-17 12:46 ` Jonathan Wakely
2022-08-17 12:55 ` Jonathan Wakely [this message]
2022-08-17 13:11 ` Aaron Gray
2022-08-17 14:19 ` Richard Earnshaw
2022-08-17 20:22 ` Jonathan Wakely
2022-09-04 17:25 ` Aaron Gray
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='CAH6eHdSLzKGXbByEPTzT3t=f_MjVJNzA_RQphvvJnTpnOuV+iA@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=aaronngray.lists@gmail.com \
--cc=gcc@gcc.gnu.org \
/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).