The GCC 7 branch is now frozen for preparation of a release candidate
for the final release from the branch, GCC 7.5. All commits require
release manager approval from now on, ideally there will be no
further commits to the branch since the branch will be closed after
the GCC 7.5 release.
Thank
Hi,
on 2019/11/4 下午6:29, Richard Earnshaw (lists) wrote:
> With the move to git fairly imminent now it would be nice if we could agree
> on a more git-friendly style of commit messages; and, ideally, start using
> them now so that the converted repository can benefit from this.
>
> Some tools,
Hello,
I would like to know how to download gcc 9.2 in windows from here.
https://ftp.gnu.org/gnu/gcc/gcc-9.2.0/
Thanks.
On Mon, Nov 04, 2019 at 05:42:47PM +, Joseph Myers wrote:
> This is also why I don't care for [PATCH] tags at the
> start of subject lines - they take away space for saying what the patch is
> about, and on gcc-patches we can expect things are patches, [PATCH]
> doesn't add useful informatio
On Mon, Nov 04, 2019 at 01:43:17PM +0100, Martin Jambor wrote:
> On Mon, Nov 04 2019, Richard Earnshaw (lists) wrote:
> > Some tools, particularly gitk or git log --oneline, can use one-line
> > summaries from a commit's log message when listing commits. It would be
> > nice if we could start ad
On Mon, 4 Nov 2019, Segher Boessenkool wrote:
> On Mon, Nov 04, 2019 at 04:19:25PM +, Jonathan Wakely wrote:
> > I've already proposed a more specific format for libstdc++:
> > https://gcc.gnu.org/ml/libstdc++/2019-09/msg00122.html
>
> PR libstdc++/12345 takes up the first 19 chars of the sho
On Mon, Nov 04, 2019 at 04:19:25PM +, Jonathan Wakely wrote:
> I've already proposed a more specific format for libstdc++:
> https://gcc.gnu.org/ml/libstdc++/2019-09/msg00122.html
PR libstdc++/12345 takes up the first 19 chars of the short subject,
adding no useful information (unless the read
On Sat, 2 Nov 2019, Eric S. Raymond wrote:
> Joseph Myers :
> > And here are corresponding lists of tags where the commit cvs2svn
> > generated for the tag should be reparented.
>
> Make that issue 2, please.
Done.
> Also, open an issue 3 about how you want those
> mid-branch deletes handled.
On 04/11/2019 16:19, Jonathan Wakely wrote:
On Mon, 4 Nov 2019 at 10:29, Richard Earnshaw (lists)
wrote:
With the move to git fairly imminent now it would be nice if we could
agree on a more git-friendly style of commit messages; and, ideally,
start using them now so that the converted reposit
On Mon, 4 Nov 2019 at 10:29, Richard Earnshaw (lists)
wrote:
>
> With the move to git fairly imminent now it would be nice if we could
> agree on a more git-friendly style of commit messages; and, ideally,
> start using them now so that the converted repository can benefit from this.
>
> Some tool
On 04/11/2019 16:04, Jeff Law wrote:
On 11/4/19 3:29 AM, Richard Earnshaw (lists) wrote:
With the move to git fairly imminent now it would be nice if we could
agree on a more git-friendly style of commit messages; and, ideally,
start using them now so that the converted repository can benefit fr
On 11/4/19 3:29 AM, Richard Earnshaw (lists) wrote:
> With the move to git fairly imminent now it would be nice if we could
> agree on a more git-friendly style of commit messages; and, ideally,
> start using them now so that the converted repository can benefit from
> this.
>
> Some tools, partic
On Mon, Nov 4, 2019 at 7:06 AM wrote:
> > From: Martin Liška
> > Sent: Monday, November 4, 2019 4:20 AM
> > To: taylor, david; gcc@gcc.gnu.org
> > Subject: Re: GCC's instrumentation and the target environment
>
> > On 11/1/19 7:13 PM, David Taylor wrote:
>
> > Hello.
>
> Hello.
>
> > > What I'd
> From: Martin Liška
> Sent: Monday, November 4, 2019 4:20 AM
> To: taylor, david; gcc@gcc.gnu.org
> Subject: Re: GCC's instrumentation and the target environment
> On 11/1/19 7:13 PM, David Taylor wrote:
> Hello.
Hello.
> > What I'd like is a stable API between the routines that 'collect' the
On Mon, Nov 04 2019, Richard Earnshaw (lists) wrote:
> Some tools, particularly gitk or git log --oneline, can use one-line
> summaries from a commit's log message when listing commits. It would be
> nice if we could start adopting a style that is compatible with this, so
> that in future commi
> With the move to git fairly imminent now it would be nice if we
> could agree on a more git-friendly style of commit messages; and,
> ideally, start using them now so that the converted repository can
> benefit from this.
>
> Some tools, particularly gitk or git log --oneline, can use one-line
>
With the move to git fairly imminent now it would be nice if we could
agree on a more git-friendly style of commit messages; and, ideally,
start using them now so that the converted repository can benefit from this.
Some tools, particularly gitk or git log --oneline, can use one-line
summaries
On 11/1/19 7:13 PM, David Taylor wrote:
I wish to use GCC based instrumentation on an embedded target. And I
am finding that GCC's libgcov.a is not well suited to my needs.
Ideally, all the application entry points and everthing that knows
about the internals of the implementation would be in s
18 matches
Mail list logo
