Re: Uninit warnings due to optimizing short-circuit conditionals

2022-02-15 Thread Mark Wielaard
Hi Richard, On Tue, 2022-02-15 at 08:25 +0100, Richard Biener wrote: > On Mon, Feb 14, 2022 at 6:38 PM Mark Wielaard wrote: > > Yes. valgrind keeps track of uninitialized bits and propagates them > > around till "use". Where use is anything that might alter the > > observable behavior of the prog

Request easy bug fix

2022-02-15 Thread Baruch Burstein via Gcc
Hi, I hope it is not inappropriate to call attention to a specific bug. https://gcc.gnu.org/bugzilla//show_bug.cgi?id=85487. I tried to do it myself, but got lost on the part where I needed to compile gcc 3 times and compare test results to some (un)known test results. It was too much time and set

Re: Request easy bug fix

2022-02-15 Thread Jonathan Wakely via Gcc
On Tue, 15 Feb 2022 at 12:34, Baruch Burstein via Gcc wrote: > Hi, > > I hope it is not inappropriate to call attention to a specific bug. > https://gcc.gnu.org/bugzilla//show_bug.cgi?id=85487. > I tried to do it myself, but got lost on the part where I needed to > compile gcc 3 times and compare

Re: Uninit warnings due to optimizing short-circuit conditionals

2022-02-15 Thread Julian Seward via Gcc
Sorry for the delayed response. I've been paging this all back in. I first saw this problem when memcheck-ing Firefox as compiled by Clang, some years back. Not long after GCC was also at it. The transformation in question is (at the C level): A && B ==> B && A if it can be proved that A

Re: Uninit warnings due to optimizing short-circuit conditionals

2022-02-15 Thread Richard Biener via Gcc
On Tue, Feb 15, 2022 at 2:00 PM Julian Seward wrote: > > Sorry for the delayed response. I've been paging this all back in. > > I first saw this problem when memcheck-ing Firefox as compiled by Clang, some > years back. Not long after GCC was also at it. The transformation in > question is (at

Re: Request easy bug fix

2022-02-15 Thread David Malcolm via Gcc
On Tue, 2022-02-15 at 12:55 +, Jonathan Wakely via Gcc wrote: > On Tue, 15 Feb 2022 at 12:34, Baruch Burstein via Gcc < > gcc@gcc.gnu.org> > wrote: > > > Hi, > > > > I hope it is not inappropriate to call attention to a specific bug. > > https://gcc.gnu.org/bugzilla//show_bug.cgi?id=85487. >

Benchmark recommendations needed

2022-02-15 Thread Andras Tantos
Hello all! I'm working on porting GCC to a new processor architecture. I think I've finally got to a fairly stable stage, so the next logical step would be to test and optimize. For that, I would need some benchmarks, and this is where I'm seeking your help. This being a hobby project, I can't sh

Re: Benchmark recommendations needed

2022-02-15 Thread Richard Biener via Gcc
On Tue, Feb 15, 2022 at 3:25 PM Andras Tantos wrote: > > Hello all! > > I'm working on porting GCC to a new processor architecture. I think > I've finally got to a fairly stable stage, so the next logical step > would be to test and optimize. For that, I would need some benchmarks, > and this is w

Re: Request easy bug fix

2022-02-15 Thread Jonathan Wakely via Gcc
On Tue, 15 Feb 2022 at 13:58, David Malcolm wrote: > On Tue, 2022-02-15 at 12:55 +, Jonathan Wakely via Gcc wrote: > > On Tue, 15 Feb 2022 at 12:34, Baruch Burstein via Gcc < > > gcc@gcc.gnu.org> > > wrote: > > > > > Hi, > > > > > > I hope it is not inappropriate to call attention to a specif

Invitation to join globaldce-newsletter

2022-02-15 Thread globaldce-newsletter via Gcc
Hi gcc@gcc.gnu.org, han.zhang...@gmail.com invited you to join the globaldce-newsletter group. https://groups.google.com/d/forum/globaldce-newsletter Message from han.zhang...@gmail.com: You are hereby invited to join globaldce-newsletter googlegroup to get regular updates on our giveaways, eve

Re: Uninit warnings due to optimizing short-circuit conditionals

2022-02-15 Thread David Malcolm via Gcc
On Tue, 2022-02-15 at 14:28 +0100, Richard Biener wrote: > On Tue, Feb 15, 2022 at 2:00 PM Julian Seward > wrote: > > > > Sorry for the delayed response.  I've been paging this all back in. > > > > I first saw this problem when memcheck-ing Firefox as compiled by > > Clang, some > > years back.