Re: Coding style for C++ constructs going forward

2020-08-12 Thread Liu Hao via Gcc
在 2020/8/13 上午2:40, David Blaikie 写道: > > Then use of `auto*` would make it easier for you to spot use of plain > pointers in your projects & scrutinize them further? > My point is that `auto*` conveys no more information than `auto`. The absence of `*` does not imply the object (pointer) being

Re: Problem with 64-bit only compiler build

2020-08-12 Thread Paul Smith
On Wed, 2020-08-12 at 15:05 -0500, Segher Boessenkool wrote: > > As usual I've built my own version of GCC, and then I check it into > > Git so that all builds can use this one canonical compiler > > regardless of operating system, etc. > > There's your problem. Git is not an archiver. Git does

C:\Program Files (x86)\Dev-Cpp\MinGW64\x86_64-w64-mingw32\lib32\libmingw32.a(lib32_libmingw32_a-crt0_c.o) In function `main': 18 C:\crossdev\src\mingw-w64-v3-git\mingw-w64-crt\crt\crt0_c.c undefined r

2020-08-12 Thread Partha paul via Gcc

Re: Silly question about pass numbers

2020-08-12 Thread Richard Biener via Gcc
On August 13, 2020 2:57:04 AM GMT+02:00, Gary Oblock via Gcc wrote: >Segher, > >If this was on the mainline and not in the middle of a >nontrivial optimization effort I would have filed a bug report >and not asked a silly question. 😉 > >I'm at a total lost as to how I could have caused the pass >

Re: Silly question about pass numbers

2020-08-12 Thread Gary Oblock via Gcc
Segher, If this was on the mainline and not in the middle of a nontrivial optimization effort I would have filed a bug report and not asked a silly question. 😉 I'm at a total lost as to how I could have caused the pass numbers to be backward... but at least have I confirmed that's what seems to b

Re: Silly question about pass numbers

2020-08-12 Thread Segher Boessenkool
Hi! On Wed, Aug 12, 2020 at 08:26:34PM +, Gary Oblock wrote: > The files are from the same run: > -rw-rw-r-- 1 gary gary 3855 Aug 12 12:49 exe.ltrans0.ltrans.074i.cp > -rw-rw-r-- 1 gary gary 16747 Aug 12 12:49 > exe.ltrans0.ltrans.087i.structure-reorg > > By the time .cp was created inlinin

Re: Silly question about pass numbers

2020-08-12 Thread Gary Oblock via Gcc
Segher, First, thanks for replying. The files are from the same run: -rw-rw-r-- 1 gary gary 3855 Aug 12 12:49 exe.ltrans0.ltrans.074i.cp -rw-rw-r-- 1 gary gary 16747 Aug 12 12:49 exe.ltrans0.ltrans.087i.structure-reorg By the time .cp was created inlining results in only main existing. In the

Re: Silly question about pass numbers

2020-08-12 Thread Segher Boessenkool
On Tue, Aug 11, 2020 at 08:27:29PM +, Gary Oblock via Gcc wrote: > For these two dump files: > > exe.ltrans0.ltrans.074i.cp > > and > > exe.ltrans0.ltrans.087i.structure-reorg > > doesn't the ".074i." mean that this dump was created > before the ".087i." dump? It means that the 074 pass is

Re: Problem with 64-bit only compiler build

2020-08-12 Thread Segher Boessenkool
On Tue, Aug 11, 2020 at 08:01:55PM -0400, Paul Smith wrote: > This is a kind of esoteric problem, but all the more annoying for that. :-) > As usual I've built my own version of GCC, and then I check it into Git > so that all builds can use this one canonical compiler regardless of > operating sy

Re: Problem with 64-bit only compiler build

2020-08-12 Thread Jonathan Wakely via Gcc
On Wed, 12 Aug 2020 at 17:43, Paul Smith wrote: > However, the lib directory is empty in my build. What lives in your > version of lib? All the runtime libs, but I think that's because mingw doesn't use the lib/lib64 split. $ ls -1 ~/gcc/mingw/x86_64-w64-mingw32/lib/ libatomic-1.dll libatomic.a

Re: Coding style for C++ constructs going forward

2020-08-12 Thread David Blaikie via Gcc
On Tue, Aug 11, 2020 at 7:49 PM Liu Hao via Gdb wrote: > > 在 2020/8/11 下午9:55, Nathan Sidwell 写道: > > > > I agree, it's the way I use auto. I particularly like the > >auto *foo = expr; > > idiom, when you're getting a pointer, but the type of the pointee is clear. > > It informs how you use

Privacy violation

2020-08-12 Thread AboTurki alawad via Gcc
My privacy was violated by an anonymous person by hacking Mobily and stealing all my information, my files and my private data, and web pages were opened with all of my data. Please help me to delete the forged certificate presented to him and delete my entire data from the site and withdraw the fo

Re: Problem with 64-bit only compiler build

2020-08-12 Thread Paul Smith
On Wed, 2020-08-12 at 16:53 +0100, Jonathan Wakely wrote: > On Wed, 12 Aug 2020 at 14:33, Paul Smith > wrote: > > > I'm not talking about PREFIX/lib, though. As can be seen from my > > question I'm talking about PREFIX///lib. This is > > where GCC keeps its own internal libraries, > > Not by d

Re: Problem with 64-bit only compiler build

2020-08-12 Thread Jonathan Wakely via Gcc
On Wed, 12 Aug 2020 at 14:33, Paul Smith wrote: > > I'm not talking about PREFIX/lib, though. > > As can be seen from my question I'm talking about > PREFIX///lib. This is where GCC keeps its own > internal libraries, Not by default, it isn't. I'm not sure what directory that is, but none of my

Re: Problem with 64-bit only compiler build

2020-08-12 Thread Paul Smith
On Wed, 2020-08-12 at 15:37 +0200, Jakub Jelinek wrote: > The important thing is that GCC wants to be relocatable, so most > paths are not hardcoded into the compiler, but depend on where the > gcc driver actually is. One can then just move the whole gcc tree > somewhere else and it should still w

Re: ** POTENTIAL FRAUD ALERT - RED HAT ** Re: Problem with 64-bit only compiler build

2020-08-12 Thread Jakub Jelinek via Gcc
On Wed, Aug 12, 2020 at 09:33:05AM -0400, Paul Smith wrote: > As someone who takes a lot of advantage of the flexibility that tools > like GCC provide I'm wary of reducing that flexibility. On the other > hand I'm not sure that breaking up the internal structure of GCC's > installation via symlink

Re: Problem with 64-bit only compiler build

2020-08-12 Thread Paul Smith
On Wed, 2020-08-12 at 15:08 +0200, Jakub Jelinek wrote: > > I think it's worth adding this to bugzilla. Depending on the > > existence of empty directories seems less than ideal. > > But canonicalizing the paths without taking the filesystem state into > account will significantly change the behav

Re: Problem with 64-bit only compiler build

2020-08-12 Thread Jakub Jelinek via Gcc
On Wed, Aug 12, 2020 at 01:08:53PM +0100, Jonathan Wakely via Gcc wrote: > > Oddly, I looked through the gnulib library and didn't find any > > appropriate module for this. It seems like there should be one. > > C++17 provides std::filesystem::weakly_canonical for that. It doesn't > help GCC or g

Re: Problem with 64-bit only compiler build

2020-08-12 Thread Jonathan Wakely via Gcc
On Wed, 12 Aug 2020 at 01:02, Paul Smith wrote: > > This is a kind of esoteric problem, but all the more annoying for that. > > As usual I've built my own version of GCC, and then I check it into Git > so that all builds can use this one canonical compiler regardless of > operating system, etc. >