[PATCH] Fix typo and avoid possible memory leak

Hi, Function average_num_loop_insns forgets to free loop body in early return. Besides, overflow comparison checks 100 (e6) but the return value is 10 (e5), I guess it's unexpected, a typo? Bootstrapped and regress tested on powerpc64le-linux-gnu. I guess this should go to GCC11? Is i

Re: [PATCH v7] Missed function specialization + partial devirtualization

On 2020/1/10 19:08, Jan Hubicka wrote: > OK. You will need to do the obvious updates for Martin's patch > which turned some member functions into static functions. > > Honza Thanks a lot! Rebased & updated, will commit below patch shortly when git push is ready. v8: 1. Rebase to master with

Re: [PATCH GCC11]Improve uninitialized warning with value range info

-- Sender:Richard Biener Sent At:2020 Jan. 9 (Thu.) 20:01 Recipient:Bin.Cheng Cc:bin.cheng ; GCC Patches Subject:Re: [PATCH GCC11]Improve uninitialized warning with value range info On Thu, Jan 9, 2020 at 11:17 AM Bin.Cheng wrot

Re: [PATCH] Document how to use --reference

On Sun, Jan 12, 2020 at 08:51:28PM +0100, Andreas Schwab wrote: > On Jan 12 2020, Andi Kleen wrote: > > > By popular demand, I did some updates to the git documentation how > > to use --reference to save disk space. > > I would advice against using --reference. Nowadays, git worktree is a > much

Re: [PATCH] Document how to use --reference

On Sun, Jan 12, 2020 at 09:51:22PM +0100, Gerald Pfeifer wrote: > On Sun, 12 Jan 2020, Andi Kleen wrote: > > By popular demand, I did some updates to the git documentation how > > to use --reference to save disk space. > > > > Also recommend https instead of http (even though both are currently >

Re: [wwwdocs] Git transition - how to access private user and vendor branches

On Sun, Jan 12, 2020 at 01:31:13PM +, Iain Sandoe wrote: > Segher Boessenkool wrote: > > Why would people want to name their local branches "me/thing" instead > > of just "thing", btw? > > it’s a way of making things distinct and allows the push rule to be present > for them > but absent f

Re: [wwwdocs] Add AVR news.

On Fri, 10 Jan 2020, Georg-Johann Lay wrote: > Added the following change to the v10 changes site. Thank you. I applied the patch below to address some issues; please let me know if you have any questions or disagree with any of it. Gerald - Log --

Re: [PATCH] Document how to use --reference

On Sun, 12 Jan 2020, Andi Kleen wrote: > By popular demand, I did some updates to the git documentation how > to use --reference to save disk space. > > Also recommend https instead of http (even though both are currently > broken) Thank you, Andi. Why https over http in this case? Isn't git it

Re: [wwwdocs] Git transition - how to access private user and vendor branches

On 1/11/20 10:54 AM, Richard Earnshaw (lists) wrote: On 11/01/2020 15:41, Segher Boessenkool wrote: Hi Richard, On Thu, Jan 09, 2020 at 04:50:03PM +, Richard Earnshaw (lists) wrote: Given the proposed intention to use non-standard refspecs for private and vendor branches I've written some

Re: [PATCH] doc: Note that some warnings depend on optimizations (PR 92757)

On Mon, 2 Dec 2019, Jonathan Wakely wrote: > PR driver/92757 > * doc/invoke.texi (Warning Options): Add caveat about some warnings > depending on optimization settings. > > The bug reporter wants this clarified. I'm not entirely convinced it's > necessary, but it doesn't seem to

Re: [PATCH] Document how to use --reference

On Jan 12 2020, Andi Kleen wrote: > By popular demand, I did some updates to the git documentation how > to use --reference to save disk space. I would advice against using --reference. Nowadays, git worktree is a much safer option. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fi

[PATCH] Document how to use --reference

From: Andi Kleen By popular demand, I did some updates to the git documentation how to use --reference to save disk space. Also recommend https instead of http (even though both are currently broken) --- htdocs/git.html | 15 --- 1 file changed, 12 insertions(+), 3 deletions(-) di

[PATCH] Document configuring your name and email address for git.

[patch, libgfortran] PR90374 Zero width format specifiers.

Hi all, The attached patch is simple enough. Zero width exponent format specifier is not allowed with "D" editing. Also, needed to adjust the width calculated for exponents greater than 999 for the larger kind cases (real 10 and real 16). Regression tested on x86_64.  I will commit as soon

Re: Add rough documentation of using git with GCC

On Fri, 10 Jan 2020, Joseph Myers wrote: > And we should also mention configuring your email address for git, if you > haven't used git on that system before or the default address you've > configured for git isn't the one you want for GCC commits. I've now applied this patch to document that.

Re: [wwwdocs] Git transition - how to access private user and vendor branches

Segher Boessenkool wrote: > Hi Richard, > > On Thu, Jan 09, 2020 at 04:50:03PM +, Richard Earnshaw (lists) wrote: >> Given the proposed intention to use non-standard refspecs for private >> and vendor branches I've written some notes on how to use these. >> >> It would be helpful if someon

RE: [RFC c-common PATCH] PR c++/40752 - useless -Wconversion with short +=.

Hi Jason, The commit Shorten right-shift again in C++. Back in SVN r131862 richi removed this code to fix PR 34235, but didn't remove the parallel code from the C front-end because the bug had previously been fixed in r44080. This patch copies the code from C again. * typeck.c (cp_buil

Re: [PATCH v3] Updated the Fix:

Jason Merrill wrote: On 11/3/19 6:42 AM, Kamlesh Kumar wrote: ChangeLog Entries: --- 2019-11-02 Kamlesh Kumar * cp-demangle.c (d_expr_primary): Handle nullptr demangling. * testsuite/demangle-expected: Added test. This test is failing in at least some pl