From: "David H. Lynch Jr." <david.lynch@sadram.net>
To: Richard Biener <richard.guenther@gmail.com>,
Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: "James K. Lowden" <jklowden@schemamania.org>, gcc@gcc.gnu.org
Subject: Re: Request for Direction.
Date: Tue, 19 Dec 2023 17:02:14 -0500 [thread overview]
Message-ID: <688dd1f280525e120a5752061090f25338601d18.camel@sadram.net> (raw)
In-Reply-To: <CAFiYyc1JziAmAr8Xgf6Wy_2M679t4iZoRd01s13RHO=O7zVf5A@mail.gmail.com>
For now I just need to be able to impliment something relatively simply
so that we can write take some existing applications - such as AI, or
sparse arrays or .... and demonstrate/test end to end our concept.
If it is successful and various others think there is a better syntax,
or means of implimenting that is a future problem.
On Mon, 2023-12-18 at 08:59 +0100, Richard Biener wrote:
> On Sat, Dec 16, 2023 at 11:53 PM Jonathan Wakely via Gcc
> <gcc@gcc.gnu.org> wrote:
> >
> > On Sat, 16 Dec 2023 at 22:41, David H. Lynch Jr. wrote:
> > > I am looking for any help I can get - pointers as to where to
> > > start
> > > with GCC, docs or howto's through to someone that wishes to
> > > participate
> > > in the project. There is a potential for compensation - we are
> > > seeking
> > > a grant, though our long term goals are partnership with a Memory
> > > vendor.
> >
> > I would start with https://gcc.gnu.org/wiki/GettingStarted
> > and the docs it links to at
> > https://gcc-newbies-guide.readthedocs.io/en/latest/
>
> You might also want to look at named address spaces, though they
> are tracked as qualifiers. Generally annotations to declarations are
> easiest as custom attributes, though I would guess you need to
> be able to annotate pointer (types) as well, thus my hint with the
> address-spaces. I guess handling all Content addressable variables
> as being in a single special address space isn't enough of
> information
> to address them.
>
> Richard.
>
> > This list is the place to ask if you get stuck, or the #gcc channel
> > on
> > the OFTC IRC network.
prev parent reply other threads:[~2023-12-19 22:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 19:43 David H. Lynch Jr.
2023-12-15 1:50 ` James K. Lowden
2023-12-16 22:41 ` David H. Lynch Jr.
2023-12-16 22:51 ` Jonathan Wakely
2023-12-18 7:59 ` Richard Biener
2023-12-19 21:58 ` David H. Lynch Jr.
2023-12-19 22:02 ` David H. Lynch Jr. [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=688dd1f280525e120a5752061090f25338601d18.camel@sadram.net \
--to=david.lynch@sadram.net \
--cc=gcc@gcc.gnu.org \
--cc=jklowden@schemamania.org \
--cc=jwakely.gcc@gmail.com \
--cc=richard.guenther@gmail.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).