Re: [PATCH] Port GCC documentation to Sphinx

2021-06-29 Thread Martin Liška
On 6/28/21 5:33 PM, Joseph Myers wrote: Are formatted manuals (HTML, PDF, man, info) corresponding to this patch version also available for review? I've just uploaded them here: https://splichal.eu/gccsphinx-final/ Martin

Re: [PATCH] Port GCC documentation to Sphinx

2021-06-29 Thread Richard Earnshaw via Gcc
On 29/06/2021 11:09, Martin Liška wrote: On 6/28/21 5:33 PM, Joseph Myers wrote: Are formatted manuals (HTML, PDF, man, info) corresponding to this patch version also available for review? I've just uploaded them here: https://splichal.eu/gccsphinx-final/ Martin In the HTML version of t

Re: Using source-level annotations to help GCC detect buffer overflows

2021-06-29 Thread David Brown
On 28/06/2021 21:06, Martin Sebor via Gcc wrote: > 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:/

Unique identifier across different partitions (LTO)

2021-06-29 Thread Erick Ochoa via Gcc
Hello, I'm trying to generate unique identifiers for some trees at link time. I understand that there are already some unique identifiers in declarations (DECL_UID) and perhaps others. Do all trees have unique identifiers or only declarations? Alternatively, if they don't have unique identifiers,

Re: Unique identifier across different partitions (LTO)

2021-06-29 Thread Martin Liška
Hi. Has anyone had any experience doing something similar? I would be interested in seeing similar examples and use cases. You likely need something similar to what I need: https://gcc.gnu.org/pipermail/gcc-patches/2021-May/570953.html Martin Thanks!

Re: Using source-level annotations to help GCC detect buffer overflows

2021-06-29 Thread Martin Sebor via Gcc
On 6/29/21 6:27 AM, David Brown wrote: On 28/06/2021 21:06, Martin Sebor via Gcc wrote: 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

Re: GCC documentation: porting to Sphinx

2021-06-29 Thread Arnaud Charlet
> >In particular can you explain the motivation behind all the changes in the > >gcc/ada/doc directory? > > Sure: > 1) All Sphinx manuals live in a directory where index page is called > index.rst. That's why > I moved e.g. this: gcc/ada/doc/{gnat_rm.rst => gnat_rm/index.rst} > 2) I moved latex_e

Re: daily report on extending static analyzer project [GSoC]

2021-06-29 Thread Ankur Saini via Gcc
AIM for today : - filter out the the nodes which already have an supergraph edge representing the call to avoid creating another edge for call - create enode for destination - create eedge representing the call itself — PROGRESS : - in order to filter out only the relevant edges, I simply use

Re: [PATCH] Port GCC documentation to Sphinx

2021-06-29 Thread Eli Zaretskii via Gcc
> From: Martin Liška > Date: Tue, 29 Jun 2021 12:09:23 +0200 > Cc: GCC Development , gcc-patc...@gcc.gnu.org > > On 6/28/21 5:33 PM, Joseph Myers wrote: > > Are formatted manuals (HTML, PDF, man, info) corresponding to this patch > > version also available for review? > > I've just uploaded them

Re: [PATCH] Port GCC documentation to Sphinx

2021-06-29 Thread Eli Zaretskii via Gcc
> Date: Tue, 29 Jun 2021 19:57:11 +0300 > From: Eli Zaretskii via Gcc > Cc: gcc@gcc.gnu.org, gcc-patc...@gcc.gnu.org, jos...@codesourcery.com > > Or how about this: > > `Overall Options' > >See Options Controlling the Kind of Output. > >*note -c. *note -S. *note -E. *note -o.

Re: Using source-level annotations to help GCC detect buffer overflows

2021-06-29 Thread David Brown
On 29/06/2021 17:50, Martin Sebor wrote: > On 6/29/21 6:27 AM, David Brown wrote: >> On 28/06/2021 21:06, Martin Sebor via Gcc wrote: >>> 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, -

Re: daily report on extending static analyzer project [GSoC]

2021-06-29 Thread David Malcolm via Gcc
On Tue, 2021-06-29 at 22:04 +0530, Ankur Saini wrote: > AIM for today : > > - filter out the the nodes which already have an supergraph edge > representing the call to avoid creating another edge for call > - create enode for destination > - create eedge representing the call itself > > — > > P

Re: replacing the backwards threader and more

2021-06-29 Thread Martin Sebor via Gcc
On 6/28/21 6:32 PM, Aldy Hernandez wrote: 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. I see. I just tested it and my patch does let the existing #pragma suppress the warn

Re: [PATCH] Port GCC documentation to Sphinx

2021-06-29 Thread Martin Liška
On 6/29/21 12:50 PM, Richard Earnshaw wrote: On 29/06/2021 11:09, Martin Liška wrote: On 6/28/21 5:33 PM, Joseph Myers wrote: Are formatted manuals (HTML, PDF, man, info) corresponding to this patch version also available for review? I've just uploaded them here: https://splichal.eu/gccsphi

Re: replacing the backwards threader and more

2021-06-29 Thread Aldy Hernandez via Gcc
On 6/30/21 12:16 AM, Martin Sebor wrote: On 6/28/21 6:32 PM, Aldy Hernandez wrote: 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. I see.  I just tested it and my patch do