On Fri, Jun 25, 2021 at 6:20 PM Aldy Hernandez wrote:
>
> Hi folks.
>
> I'm done with benchmarking, testing and cleanups, so I'd like to post my
> patchset for review. However, before doing so, I'd like to address a
> handful of meta-issues that may affect how I post these patches.
First of all
> I've got something that is very close to be a patch candidate that can be
> eventually merged. Right now, the patches are available here:
> https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;a=log;h=refs/users/marxin/heads/sphinx-v3
FWIW I would prefer to review the changes posted here directly with a
On 6/28/21 12:23 PM, Arnaud Charlet wrote:
I've got something that is very close to be a patch candidate that can be
eventually merged. Right now, the patches are available here:
https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;a=log;h=refs/users/marxin/heads/sphinx-v3
FWIW I would prefer to review
Hi everyone,
It is that time again and we will be having our 4th community call over
on Jitsi for the first Friday of the month.
* Date: 2nd July 2021
o UTC: 0900
o UK/Ireland UTC+1/BST: 1000
o Central European Summer Time UTC+2: 1100
* Monthly Report: WIP
* Agenda (WIP):
Hello.
I'm sending the complete patch set that includes ChangeLog entries.
Unfortunately,
majority of the patches are huge, that's why I sent like to a tarball:
https://splichal.eu/tmp/port-to-sphinx-v1.tar
The tarball contains the following patches:
19e06194746 Ada: port to Sphinx.
9a744ca431
On 6/28/21 10:22 AM, Richard Biener wrote:
On Fri, Jun 25, 2021 at 6:20 PM Aldy Hernandez wrote:
Hi folks.
I'm done with benchmarking, testing and cleanups, so I'd like to post my
patchset for review. However, before doing so, I'd like to address a
handful of meta-issues that may affect h
On 28/06/2021 14:49, Philip Herron wrote:
> Hi everyone,
>
> In Rust the language has the notion of the unit type '()', so for example:
>
> fn foo ->i32 { ... }
> fn bar() { ... }
>
> Foo has the return type i32, and bar has no return type, which means it
> is unit-type so that it can be a value
> On 28-Jun-2021, at 12:18 AM, David Malcolm wrote:
>>
>>>
Q. But even if we find out which function to call, how will the
analyzer know which snode does that function belong ?
>>>
>>> Use this method of supergraph:
>>> supernode *get_node_for_function_entry (function *fun)
Are formatted manuals (HTML, PDF, man, info) corresponding to this patch
version also available for review?
--
Joseph S. Myers
jos...@codesourcery.com
On Mon, Jun 28, 2021 at 02:51:22PM +0100, Philip Herron wrote:
> On 28/06/2021 14:49, Philip Herron wrote:
> > In Rust the language has the notion of the unit type '()', so for example:
> >
> > fn foo ->i32 { ... }
> > fn bar() { ... }
> >
> > Foo has the return type i32, and bar has no return ty
I wrote an article for the Red Hat Developer blog about how
to annotate code to get the most out of GCC's access checking
warnings like -Warray-bounds, -Wformat-overflow, and
-Wstringop-overflow. The article published last week:
https://developers.redhat.com/articles/2021/06/25/use-source-level-
On 6/28/21 12:17 AM, Aldy Hernandez wrote:
On 6/25/21 7:19 PM, Martin Sebor wrote:
On 6/25/21 10:20 AM, Aldy Hernandez via Gcc wrote:
Hi folks.
I'm done with benchmarking, testing and cleanups, so I'd like to post
my patchset for review. However, before doing so, I'd like to
address a han
On Mon, 2021-06-28 at 20:23 +0530, Ankur Saini wrote:
>
>
> > On 28-Jun-2021, at 12:18 AM, David Malcolm
> > wrote:
> > >
> > > >
> > > > >
> > > > > Q. But even if we find out which function to call, how will
> > > > > the
> > > > > analyzer know which snode does that function belong ?
> > >
I had changed my approach to passing -Wno-free-nonheap-object in the
Makefile. Can you try disabling the Makefile bit and bootstrapping, cause
that was still failing.
Thanks.
Aldy
On Tue, Jun 29, 2021, 00:29 Martin Sebor wrote:
> On 6/28/21 12:17 AM, Aldy Hernandez wrote:
> >
> >
> > On 6/25/21
14 matches
Mail list logo
