Re: [GSoC][Static Analyzer] Some questions and request for a small patch to work on

[Iain Sandoe <idsandoe@googlemail.com>]

Hi Shengyu,

> On 22 Feb 2023, at 14:11, Shengyu Huang via Gcc <gcc@gcc.gnu.org> wrote:
> 
>> IIRC I saw you post a few days ago about trying to build gcc on your M2
>> laptop; did you manage this?  Building GCC trunk from a git checkout,
>> and hacking in a "hello world" warning would be a great place to start.
>> See the guide above for some hints on how to make this process quicker,
>> and let me know if you need help if you run into difficulties.  Given
>> that the analyzer is about emitting warnings, rather than generating
>> code, it may be that although we don't yet fully support your hardware,
>> we *might* already support it enough to allow for hacking on the
>> analyzer, perhaps with some judicious choices of "configure" options.
> 
> I just finished building it today on my laptop (Thanks Iain!). The GCC-12 branch did not work (I got `configure: error: C preprocessor "/lib/cpp" fails sanity check`)

Possibly my bad - there are some additional fixes needed for newer Darwin on the 12 branch (I need to re-release 12.1 Darwin):

https://github.com/iains/gcc-12-branch/tree/gcc-12-1-darwin-pre-r1 
If that doesn’t work please file an issue.

> but the development branch works for me (haven’t encountered the potential pitfalls mentioned yet after testing it with some simple programs).

In general, new work needs to be on trunk anyway - so that this would probably be what you would use.

Note: I _rebase_ the work onto latest trunk from time to time .. (actually overdue at the moment) so you have to keep an eye out for that .

good luck with the GSoC application!
Iain