On Mon, 2021-07-05 at 21:45 +0530, Ankur Saini wrote:
> I forgot to send the daily report yesterday, so this one covers the
> work done on both days
>
> AIM :
>
> - make the analyzer call the function with the updated call-string
> representation ( even the ones that doesn’t have a superedge )
>
On Tue, 2021-07-06 at 18:46 -0400, David Malcolm wrote:
> On Sat, 2021-07-03 at 20:07 +0530, Ankur Saini wrote:
> > AIM for today :
> >
> > - update the call_stack to track something else other than
> > supergraph
> > edges
> >
> > —
> >
> > PROGRESS :
> >
> > - After some brainstorming about
On Sat, 2021-07-03 at 20:07 +0530, Ankur Saini wrote:
> AIM for today :
>
> - update the call_stack to track something else other than supergraph
> edges
>
> —
>
> PROGRESS :
>
> - After some brainstorming about tracking the callstack, I think one
> better way to track the call stack is to kee
On Tue, 6 Jul 2021, 22:45 Martin Sebor via Gcc, wrote:
> On 7/6/21 3:36 PM, Marek Polacek wrote:
> > On Tue, Jul 06, 2021 at 03:20:26PM -0600, Martin Sebor via Gcc wrote:
> >> I came away from the recent discussion of ChangeLogs requirements
> >> with the impression that the PR bit should be
On 7/6/21 3:36 PM, Marek Polacek wrote:
On Tue, Jul 06, 2021 at 03:20:26PM -0600, Martin Sebor via Gcc wrote:
I came away from the recent discussion of ChangeLogs requirements
with the impression that the PR bit should be in the subject
(first) line and also above the ChangeLog part but does
On Tue, Jul 06, 2021 at 03:20:26PM -0600, Martin Sebor via Gcc wrote:
> I came away from the recent discussion of ChangeLogs requirements
> with the impression that the PR bit should be in the subject
> (first) line and also above the ChangeLog part but doesn't need
> to be repeated again in th
I came away from the recent discussion of ChangeLogs requirements
with the impression that the PR bit should be in the subject
(first) line and also above the ChangeLog part but doesn't need
to be repeated again in the ChangeLog entries. But my commit
below was rejected last Friday with the s
Status
==
The GCC 11 branch is open for regression and documentation fixes.
It's time for a GCC 11.2 release and we are aiming for a release
candidate in about two weeks which would result in the GCC 11.2
release about three months after GCC 11.1.
Two weeks give you ample time to care for i
