On Wed, 2023-03-01 at 12:16 +0100, Shengyu Huang wrote:
> Hi Dave,
>
> > On 1 Mar 2023, at 00:59, David Malcolm wrote:
> >
> > Did you get it to output your messages?
> >
>
>
> Yes, I chose to emit the warning before the supergraph or exploded
> graph is created (I guess this is enough, right
Hi Dave,
> On 1 Mar 2023, at 00:59, David Malcolm wrote:
>
> Did you get it to output your messages?
>
Yes, I chose to emit the warning before the supergraph or exploded graph is
created (I guess this is enough, right?). I checked out from the trunk a week
ago, and I checked out from the la
On Tue, 2023-02-28 at 10:18 +0100, Shengyu Huang wrote:
> Hi Dave,
>
> Do you want me to follow the steps 7-10
> (https://gcc-newbies-guide.readthedocs.io/en/latest/how-to-improve-th
> e-location-of-a-diagnostic.html) or tell you where I add the code
> simply? Basically, I added
>
> warning_at (D
Hi Dave,
Do you want me to follow the steps 7-10
(https://gcc-newbies-guide.readthedocs.io/en/latest/how-to-improve-the-location-of-a-diagnostic.html)
or tell you where I add the code simply? Basically, I added
warning_at (DECL_SOURCE_LOCATION (node->decl), 0, "hello world, I’m compiling
%qE",
On 27/02/2023 14:49, Iain Sandoe wrote:
Hi Shengyu,
By the way, is it expected that I need to configure with
`--with-sysroot=/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk`?
Yes.
- for some time now macOS no longer installs headers in /usr/include (and on
newer versions most of the
Hi Iain,
> On 27 Feb 2023, at 14:45, Iain Sandoe wrote:
>
> Please file an issue against the branch on github (since this is a
> development branch it’s not appropriate to use the GCC bugzilla yet).
The same error occurred for both the development branch and the gcc-12-2
branch. Should I only
Hi Shengyu,
> On 27 Feb 2023, at 13:35, Shengyu Huang via Gcc wrote:
>
> By the way, is it expected that I need to configure with
> `--with-sysroot=/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk`?
Yes.
- for some time now macOS no longer installs headers in /usr/include (and on
newer
Hi Shengyu
> On 27 Feb 2023, at 13:35, Shengyu Huang via Gcc wrote:
> Sorry for the late reply. I just built gcc-12-2 on my machine with bootstrap
> and it worked.
great,
>
> However, maybe due to some missing configuration, building without bootstrap
> does not work on my machine (developme
Hi Iain,
Sorry for the late reply. I just built gcc-12-2 on my machine with bootstrap
and it worked.
However, maybe due to some missing configuration, building without bootstrap
does not work on my machine (development branch or gcc-12-2). Specifically, my
configuration is as follows.
```
$HO
On Thu, 23 Feb 2023 at 15:57, James K. Lowden wrote:
>
> On Wed, 22 Feb 2023 14:03:36 +
> Jonathan Wakely via Gcc 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 be
On Wed, 22 Feb 2023 14:03:36 +
Jonathan Wakely via Gcc 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
On Wed, 2023-02-22 at 15:11 +0100, Shengyu Huang wrote:
> Hi Dave,
>
>
> > But a better place to look would probably be in our bugzilla; see
> > the
> > links on the wiki page:
> > https://gcc.gnu.org/wiki/StaticAnalyzer
> > The "open bugs" list currently has 41 "RFE" bugs ("request for
> > enh
Hi Shengyu,
oops finger-trouble…
> On 22 Feb 2023, at 14:53, Iain Sandoe wrote:
>> On 22 Feb 2023, at 14:11, Shengyu Huang via Gcc wrote:
>
> Possibly my bad - there are some additional fixes needed for newer Darwin on
> the 12 branch (I need to re-release 12.1 Darwin):
12.2…
> https://git
Hi Shengyu,
> On 22 Feb 2023, at 14:11, Shengyu Huang via Gcc 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.
>>
Hi Dave,
> But a better place to look would probably be in our bugzilla; see the
> links on the wiki page:
> https://gcc.gnu.org/wiki/StaticAnalyzer
> The "open bugs" list currently has 41 "RFE" bugs ("request for
> enhancement" i.e. ideas for new features), some of which might make
> suitable
On Tue, 21 Feb 2023 at 22:55, David Malcolm via Gcc 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 abo
On Tue, 2023-02-21 at 22:26 +0100, Shengyu Huang via Gcc wrote:
> Dear all,
Hi Shengyu, and welcome.
>
> I want to work on the Static Analyzer project and just started to
> read the documentation these days,
Excellent! I'm the author/maintainer of the analyzer, so I would
mentor any such GSoC
Dear all,
I want to work on the Static Analyzer project and just started to read the
documentation these days, but what’s mentioned in 27.1.6 in the internal
document
(https://gcc.gnu.org/onlinedocs/gccint/Analyzer-Internals.html#Analyzer-Internals)
seems outdated or not detailed enough. For e
18 matches
Mail list logo
