From: Joseph Watanabe <Josephw@hyvesolutions.com>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: LPC and other questions ?
Date: Mon, 25 Oct 2021 12:45:58 +0000 [thread overview]
Message-ID: <BYAPR04MB472778231A3C2A1B4DBC4946A1839@BYAPR04MB4727.namprd04.prod.outlook.com> (raw)
Hello and good morning,
Recently I had the privilege of stumbling upon a few of the videos on youtube. I really found them helpful, and learned quite a bit. I will say I probably have to watch them a few more times to even begin to have a level of understanding that everyone had years ago.... Anyway, there are a few things I noticed and wanted to reach out.
From the list of sponsors, I thought the company that I work with would be one as well, but more than likely there are no one aware.. I am not in any position to make any decisions on that level at all, but I don't think it would hurt if you could describe to me the process and I could forward that information to someone.. somewhere..
I'm not sure how all of these things would work at the moment..
Anyway, I was also wondering about rust ? I have not used it yet, usually I use gcc/gcc-c++/gcc-gfortran for most cases. Is there another webpage I could check out also?
There are also other issues that I am starting to notice and am having trouble verifying a few things, and it might or might not be good to be verified.. I don't know.. Maybe we can discuss this later sometime.
Thanks for your time,
Have a good day
-Joseph
next reply other threads:[~2021-10-25 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 12:45 Joseph Watanabe [this message]
2021-10-27 15:45 ` Martin Jambor
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=BYAPR04MB472778231A3C2A1B4DBC4946A1839@BYAPR04MB4727.namprd04.prod.outlook.com \
--to=josephw@hyvesolutions.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).