DejaGnu diagnostics checking confused, possibly related to 'dg-line'?

Hi! Help. Save the attached file as 'gcc/testsuite/c-c++-common/goacc/l_.c', and then run: $ make check-gcc-c++ RUNTESTFLAGS=--all\ goacc.exp=l_.c As expected for '-std=c++98' testing, which comes first: PASS: c-c++-common/goacc/l_.c -std=c++98 (test for errors, line 14) PASS: c-

armv7+neon bus error

Hello, I built gcc for armv7+neon target with 128-bit stack alignment to enable ASan with custom shadow memory scale. I got bus error in runtime for some of utils built with the toolchain. I checked disassembler output and found that sometimes gcc vectorizes assignments at the ASan epilogue of

Re: Incremental updating of SSA_NAMEs that are passed to b_c_p

On Fri, 2020-10-30 at 09:22 +0100, Richard Biener wrote: > On Thu, Oct 29, 2020 at 6:20 PM Ilya Leoshkevich > wrote: > > On Wed, 2020-10-28 at 12:18 +0100, Richard Biener wrote: > > > On Tue, Oct 27, 2020 at 7:36 PM Ilya Leoshkevich via Gcc > > > wrote: > > > > Hi, > > > > > > > > I'd like to re

Re: DejaGnu diagnostics checking confused, possibly related to 'dg-line'?

Hi! I've investigated some more. On 2020-11-03T13:31:53+0100, I wrote: > Help. Save the attached file as 'gcc/testsuite/c-c++-common/goacc/l_.c', > and then run: > > $ make check-gcc-c++ RUNTESTFLAGS=--all\ goacc.exp=l_.c > > As expected for '-std=c++98' testing, which comes first: > > P

Re: Dead Field Elimination and Field Reordering

On Fri, Oct 30, 2020 at 6:44 PM Erick Ochoa wrote: > > Hello again, > > I've been working on several implementations of data layout > optimizations for GCC, and I am again kindly requesting for a review of > the type escape based dead field elimination and field reorg. > > Thanks to everyone that

Re: Dead Field Elimination and Field Reordering

Thanks for the review Richard I'll address what I can. I also provide maybe some hindsight into some of the design decisions here. I'm not trying to be defensive just hoping to illuminate why some decisions were made and how some criticisms may fail to really address the reason why these design

git tag creation for misc/first-auto-changelog

Hello. I would like to create a git tag for a point when we started using automatically-generated ChangeLog files. It's: cfdff3eeb902958d3eefe60d5712d64e2367843f and I would name it something like: misc/first-auto-changelog ? Thanks, Martin

Re: gcc/DATESTAMP not updated any longer

On Mon, 2 Nov 2020, Jakub Jelinek via Gcc wrote: > It isn't that easy (because update_version_git checks the gcc trunk and > so I had to insert a sh invocation in which I've tweaked it), but it worked, > thanks. But something is really wrong with the hooks, as the gcc-cvs mail > for the trunk dai

Re: git tag creation for misc/first-auto-changelog

On Tue, 3 Nov 2020 at 17:40, Martin Liška wrote: > > Hello. > > I would like to create a git tag for a point when we started > using automatically-generated ChangeLog files. It's: > > cfdff3eeb902958d3eefe60d5712d64e2367843f > > and I would name it something like: > misc/first-auto-changelog > > ?