Re: [RFC] -Weverything

On Wed, Jan 23, 2019 at 08:17:00AM +0100, Thomas König wrote: > > > > Am 23.01.2019 um 01:53 schrieb Martin Sebor : > > > I often wish GCC supported it -- not in the hopes of finding every > > conceivable bug or transgression against known coding styles but > > as a tool to discover warnings tha

Re: [RFC] -Weverything

> Am 23.01.2019 um 01:53 schrieb Martin Sebor : > I often wish GCC supported it -- not in the hopes of finding every > conceivable bug or transgression against known coding styles but > as a tool to discover warnings that have to be explicitly enabled > either by using their own options or by s

Re: About GSOC.

I built gcc as a debuggable compiler as given using -g3. I am using gdb and loaded the cc1 using: gdb --args cc1 with output as: Successfully loaded GDB hooks for GCC But I really dont know how to inspect a file like real.h (real_value)/real.c? Thanks. -Tejas On Wed, 23 Jan 2019 at 08:28, Tej

Re: About GSOC.

> differ. (It's the unoptimized, stage1 cc1 that should be run under a > debugger. See for more details.) Hello. I normally configure GCC by (as you told) /configure --enable-languages=c,c++ --disable-bootstrap --disable-multilib And further as told in <

Ms Mayes Williams delegate under United Nations

Hello Dear, It's my pleasure to meet you. My name is Ms Mayes Williams, from UK and I work as assistant coordinator delegate to Sub-Saharan under United Nations. I got your contact online when I’m searching for someone to set a partnership establishment with in your country, the terms of investme

Re: [RFC] -Weverything

On 1/22/19 11:34 AM, Thomas Koenig wrote: Hi, What would people think about a -Weverything option which turns on every warning there is? I think that could be quite useful in some circumstances, especially to find potential bugs with warnings that people, for some reason or other, found too noi

RE: North American Farm & Power Show - Attendees Info

Hi, I hope you are the right person to discuss about North American Farm & Power Show Attendees complete info? North American Farm & Power Show of 5,000+ attendees with complete details and verified email addresses. List will be provided for unlimited usage. Interested? Email me bac

Re: testsuite result updates for x86_64-w64-mingw32

> So looking at it again, this seems to be happening during stage3. Yes, I should have realized it a while ago, you don't compile g-exptty.adb for the compiler but only for the runtime... The backtrace seems to show that the abort at libgcc/unwind-dw2.c:1386 is raised: int size = dwarf_reg_s

Re: [RFC] -Weverything

On Tue, Jan 22, 2019 at 1:35 PM Thomas Koenig wrote: > > What would people think about a -Weverything option which turns on > every warning there is? I tried to use -Weverything on a C++ project with about 350 source files. It was a failed experiment. It created too much noise to be useful. Your

Re: testsuite result updates for x86_64-w64-mingw32

Hi Eric, So looking at it again, this seems to be happening during stage3. And there aren't any special flags being set. Regards, Tamar From: Eric Botcazou Sent: Tuesday, January 22, 2019 12:23 PM To: Tamar Christina Cc: gcc@gcc.gnu.org; Óscar Fuentes; n

Re: [RFC] -Weverything

On Tue, 22 Jan 2019 at 18:56, Jonathan Wakely wrote: > > On Tue, 22 Jan 2019 at 18:46, Marc Glisse wrote: > > > > On Tue, 22 Jan 2019, Thomas Koenig wrote: > > > > > Hi, > > > > > > What would people think about a -Weverything option which turns on > > > every warning there is? > > > > > > I thin

Re: [RFC] -Weverything

On Tue, 22 Jan 2019 at 18:46, Marc Glisse wrote: > > On Tue, 22 Jan 2019, Thomas Koenig wrote: > > > Hi, > > > > What would people think about a -Weverything option which turns on > > every warning there is? > > > > I think that could be quite useful in some circumstances, especially > > to find p

Re: [RFC] -Weverything

On Tue, 22 Jan 2019, Thomas Koenig wrote: Hi, What would people think about a -Weverything option which turns on every warning there is? I think that could be quite useful in some circumstances, especially to find potential bugs with warnings that people, for some reason or other, found too no

[RFC] -Weverything

Hi, What would people think about a -Weverything option which turns on every warning there is? I think that could be quite useful in some circumstances, especially to find potential bugs with warnings that people, for some reason or other, found too noisy for -Wextra. The name could be somethin

Welcome to Shenzhen ZDCL Trade Co., Ltd.

Hi friend, Hopefully,this email doesn't cause you any inconvenience. Our company can provide you with the production of various printed circuit board. According to the design plan and the quantity of goods, the price can be completed within 2 hours at the earliest. Sample ready in 2 days,fast

RE: testsuite result updates for x86_64-w64-mingw32

> > Then, if both the base compiler and the compiler to be built are configured > that way, there is no reason why this cannot work. > > What's a little strange is that there is a .cold part in the backtrace: > > #14 0x015fd511 in uw_init_context_1.cold () at ../../../gcc-8- > 20181214/libgcc/

Re: testsuite result updates for x86_64-w64-mingw32

> It's built with --disable-sjlj-exceptions --with-dwarf2 > > https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-gcc/PKGBUILD > #L150 Then, if both the base compiler and the compiler to be built are configured that way, there is no reason why this cannot work. What's a little stran

RE: testsuite result updates for x86_64-w64-mingw32

> > Ah, that makes sense since the 32-bit SEH is different from the 64-bit > > one, explains why the 64-bit builds work. > > Which EH mechanism does the base compiler use? The default one? We > know that this works with the DWARF-2 mechanism (--disable-sjlj- > exceptions). It's built with --dis

Re: testsuite result updates for x86_64-w64-mingw32

> Ah, that makes sense since the 32-bit SEH is different from the 64-bit one, > explains why the 64-bit builds work. Which EH mechanism does the base compiler use? The default one? We know that this works with the DWARF-2 mechanism (--disable-sjlj-exceptions). -- Eric Botcazou

RE: testsuite result updates for x86_64-w64-mingw32

> -Original Message- > From: Eric Botcazou > Sent: Tuesday, January 22, 2019 11:19 > To: Tamar Christina > Cc: Óscar Fuentes ; gcc@gcc.gnu.org > Subject: Re: testsuite result updates for x86_64-w64-mingw32 > > > The gnat1 command that fails is > > > > mingw-w64-gcc/src/build-i686-w64-min

Re: testsuite result updates for x86_64-w64-mingw32

> The gnat1 command that fails is > > mingw-w64-gcc/src/build-i686-w64-mingw32/gcc/gnat1.exe -gnatwa -quiet > -nostdinc -dumpbase g-exptty.adb -auxbase-strip g-exptty.o -O2 -Wextra > -Wall -g -gnatpg -mtune=generic -march=i686 -gnatO g-exptty.o g-exptty.adb > -o E:\msys32-devel\tmp\ccAujHCD.s > >

RE: testsuite result updates for x86_64-w64-mingw32

Forwarding to list as well. > -Original Message- > From: Tamar Christina > Sent: Tuesday, January 22, 2019 11:02 > To: 'Óscar Fuentes' ; Eric Botcazou > > Cc: gcc@gcc.gnu.org > Subject: RE: testsuite result updates for x86_64-w64-mingw32 > > Hi Eric, > > This slipped my mind, but I was

Re: GCC's ICF vs. gold's ICF

On 1/15/19 4:49 PM, Richard Biener wrote: > On Tue, Jan 15, 2019 at 4:43 PM Frank Tetzel > wrote: >> why is the ICF pass in gcc not folding member functions which depend on a template parameter but happen to generate identical code? Is it because it is not identical on the IR level