From: "James K. Lowden" <jklowden@schemamania.org>
To: gcc@gcc.gnu.org
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>
Subject: Re: [GSoC][Static Analyzer] Some questions and request for a small patch to work on
Date: Thu, 23 Feb 2023 06:17:29 -0500 [thread overview]
Message-ID: <20230223061729.7e89fe3778941770ce14e122@schemamania.org> (raw)
In-Reply-To: <CAH6eHdQ4Ch+OW2wp5wtQzC5wc6Ap7V-Jc67ixiQsSVi=TWy_xg@mail.gmail.com>
On Wed, 22 Feb 2023 14:03:36 +0000
Jonathan Wakely via Gcc <gcc@gcc.gnu.org> wrote:
> I think GCC trunk won't even build on M2, you need Iain Sandoe's
> out-of-tree patches.
https://gitlab.cobolworx.com/COBOLworx/gcc-cobol/-/jobs/2822
We've been building on aarch64 based on GCC trunk since December.
--jkl
next prev parent reply other threads:[~2023-02-23 15:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 21:26 Shengyu Huang
2023-02-21 22:55 ` David Malcolm
2023-02-22 14:03 ` Jonathan Wakely
2023-02-23 11:17 ` James K. Lowden [this message]
2023-02-23 16:30 ` Jonathan Wakely
2023-02-22 14:11 ` Shengyu Huang
2023-02-22 14:53 ` Iain Sandoe
2023-02-22 15:13 ` Iain Sandoe
2023-02-27 13:35 ` Shengyu Huang
2023-02-27 13:45 ` Iain Sandoe
2023-02-27 13:51 ` Shengyu Huang
2023-02-27 13:49 ` Iain Sandoe
2023-02-27 14:01 ` Floyd, Paul
2023-02-22 15:43 ` David Malcolm
2023-02-28 9:18 ` Shengyu Huang
2023-02-28 23:59 ` David Malcolm
2023-03-01 11:16 ` Shengyu Huang
2023-03-01 13:48 ` David Malcolm
2023-02-28 14:46 ` [GSoC][Static Analyzer] Ideas for proposal Shengyu Huang
2023-03-01 0:22 ` David Malcolm
2023-03-12 22:20 ` Shengyu Huang
2023-03-13 15:51 ` David Malcolm
2023-03-20 17:28 ` [GSoC][Static Analyzer] First proposal draft and a few more questions/requests Shengyu Huang
2023-03-20 22:50 ` David Malcolm
2023-03-26 16:03 ` Shengyu Huang
2023-03-26 17:14 ` David Malcolm
2023-03-26 21:46 ` Shengyu Huang
2023-04-01 14:19 ` Shengyu Huang
2023-04-02 22:53 ` David Malcolm
2023-04-03 0:02 ` Shengyu Huang
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=20230223061729.7e89fe3778941770ce14e122@schemamania.org \
--to=jklowden@schemamania.org \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@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).