Hi Dave,
> Overall, it looks great. Some notes:
> - maybe specify the *GCC* static analyzer you first mention it
Done.
> - you talk about "timeout" warnings. The analyzer already can emit a
> "timeout" warning of sorts, via -Wanalyzer-too-complex, though this is
> based on the complexity of th
On Sat, 2023-04-01 at 20:32 +, Sun Steven via Gcc wrote:
> Hello,
Hi!
I just replied to your other email in the "[GSoC] Interest and initial
proposal for project on reimplementing cpychecker as -fanalyzer plugin
" thread.
>
> I want to take part in this project.
>
> b. Write a plugin to ad
On Sat, 2023-04-01 at 19:49 -0400, Eric Feng wrote:
> > For the task above, I think it's almost all there, it's "just" a
> > case
> > of implementing the special-case knowledge about the CPython API,
> > mostly via known_function subclasses.
>
> Sounds good.
>
>
> > In cpychecker I added some cu
On Sun, 2023-04-02 at 17:24 +, Sun Steven via Gcc wrote:
> Hi, Eric, Malcom,
Hi - and welcome to the GCC community.
>
> Sorry that I didn't check this thread before.
>
> It sounds like there are a lot of things to do. I want to offer some
> help.
>
> Let me add some backgrounds of memory m
On Sat, 2023-04-01 at 16:19 +0200, Shengyu Huang wrote:
> Hi Dave,
>
> > >
> > > I has looked into compiling those files with the patch some time
> > > ago;
> > > looking at my notes, one issue was with this on-stack buffer:
> > > char extra[1024];
> > > declared outside the loop. Inside the
On Sat, 2023-04-01 at 01:33 +0200, Benjamin Priour wrote:
> Hi David,
>
>
> On Thu, Mar 30, 2023 at 2:04 AM David Malcolm
> wrote:
> > I think working on the C++ enablement prerequisites in the analyzer
> > would make more sense. I'd planned to do this myself for GCC 14,
> > but
> > there are p
Snapshot gcc-13-20230402 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20230402/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 13 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On Sun, 2 Apr 2023, 18:31 Damian Tometzki, wrote:
> Hello together,
>
> i found a possible fix
>
> diff --git a/gcc/common/config/riscv/riscv-common.cc
> b/gcc/common/config/riscv/riscv-common.cc
> index b3c6ec97e7a..32ba1d52556 100644
> --- a/gcc/common/config/riscv/riscv-common.cc
> +++ b/gcc/c
Hello together,
i found a possible fix
diff --git a/gcc/common/config/riscv/riscv-common.cc
b/gcc/common/config/riscv/riscv-common.cc
index b3c6ec97e7a..32ba1d52556 100644
--- a/gcc/common/config/riscv/riscv-common.cc
+++ b/gcc/common/config/riscv/riscv-common.cc
@@ -1155,7 +1155,7 @@ riscv_subse
Hi, Eric, Malcom,
Sorry that I didn't check this thread before.
It sounds like there are a lot of things to do. I want to offer some help.
Let me add some backgrounds of memory management in python here.
## Intro (for people unfamiliar with CPython)
Unlike programs written in C++, where the c
Hello together,
i have the following build error gcc 13 current git:
/home/damian/data/gcc13built/./prev-gcc/xg++
-B/home/damian/data/gcc13built/./prev-gcc/
-B/usr/riscv64-linux-gnu/bin/ -nostdinc++
-B/home/damian/data/gcc13built/prev-riscv64-linux-gnu/libstdc++-v3/src/.libs
-B/home/damian/data/g
11 matches
Mail list logo
