Re: GDC environment variable - solved, but new problem

> Re GCC 9.1, however beware of > "stage1 d21 fails to link with GDC 9.1". Thanks for all who replied. Thanks especially for mentioning this problem, as my build did indeed fail with this error on GCC 9.3. I applied the fix and that's now resolved. Now I have the

Re: Naming flag for specifying the output file name for Binary Module Interface files

On 12/7/22 11:58, Iain Sandoe wrote: On 7 Dec 2022, at 16:52, Nathan Sidwell via Gcc wrote: On 12/7/22 11:18, Iain Sandoe wrote: I think it is reasonable to include c++ in the spelling, since other languages supported by GCC (and clang in due course) have modules. I disagree (about the

Re: Naming flag for specifying the output file name for Binary Module Interface files

> On 7 Dec 2022, at 16:52, Nathan Sidwell via Gcc wrote: > > On 12/7/22 11:18, Iain Sandoe wrote: > >> I think it is reasonable to include c++ in the spelling, since other >> languages supported by >> GCC (and clang in due course) have modules. > > I disagree (about the reasonableness part)

Re: Naming flag for specifying the output file name for Binary Module Interface files

On 12/7/22 11:18, Iain Sandoe wrote: I think it is reasonable to include c++ in the spelling, since other languages supported by GCC (and clang in due course) have modules. I disagree (about the reasonableness part). Other languages have modules, true, but if they want to name the output fi

Re: Naming flag for specifying the output file name for Binary Module Interface files

On 12/7/22 10:23, Jonathan Wakely wrote: On Wed, 7 Dec 2022, 02:30 chuanqi.xcq via Gcc, > wrote: \ (2) If (1) is not acceptable and we love to keep the command line consistency, I think clang can use '-fmodule-output=' as long as we make it clear in the do

Re: Naming flag for specifying the output file name for Binary Module Interface files

On Wed, Dec 07, 2022 at 16:18:00 +, Iain Sandoe wrote: > I think it is reasonable to include c++ in the spelling, since other > languages supported by > GCC (and clang in due course) have modules. Especially given that Fortran doesn't necessarily have one module to output; Fortran sources can

Re: Naming flag for specifying the output file name for Binary Module Interface files

Hi Folks, > On 7 Dec 2022, at 15:45, ben.boeckel via Gcc wrote: > > On Wed, Dec 07, 2022 at 15:23:09 +, Jonathan Wakely wrote: >> I disagree. I can easily remember "module output" but I would have to check >> the manual every time to see if it's "std c++ module save file" or some >> other pe

Re: Naming flag for specifying the output file name for Binary Module Interface files

On Wed, Dec 07, 2022 at 15:23:09 +, Jonathan Wakely wrote: > I disagree. I can easily remember "module output" but I would have to check > the manual every time to see if it's "std c++ module save file" or some > other permutation of those words I can say that in developing the CMake side of t

Re: Naming flag for specifying the output file name for Binary Module Interface files

On Wed, 7 Dec 2022, 02:30 chuanqi.xcq via Gcc, wrote: > Hi Nathan, > > 1) 'save' -- does it *cause* the bmi to be saved, or is that actually > controlled > by other options? (I suspect the latter) > Yes, it causes the bmi to be saved. In fact, when we add `-save-temps` > option in clang and we co

Re: GDC environment variable

Hi! On 2022-12-07T12:05:18+0530, Ankur Saini via Gcc wrote: >> On 07-Dec-2022, at 11:42 AM, Dave Blanchard wrote: >> >> Is there an environment variable like 'CC' or 'CXX', which specifies the >> name of the D compiler to use, which I might need to set when bootstrapping >> GCC? Thanks. > > I

Re: -fprofile-update=atomic vs. 32-bit architectures

On Wed, Dec 7, 2022 at 10:24 AM Sebastian Huber wrote: > > > > On 07.12.22 10:09, Richard Biener wrote: > > On Wed, Dec 7, 2022 at 9:51 AM Sebastian Huber > > wrote: > >> On 06.12.22 17:08, Richard Biener wrote: > >>> Likely. I'd use the gimple_build () API from gimple-fold.h which > >>> builds

Re: GDC environment variable

I expect it to be `DC`. Original Message On 7 Dec 2022, 06:11, Dave Blanchard wrote: > Is there an environment variable like 'CC' or 'CXX', which specifies the name > of the D compiler to use, which I might need to set when bootstrapping GCC? > Thanks. -- Dave Blanchard

Re: -fprofile-update=atomic vs. 32-bit architectures

On 04.11.22 09:27, Sebastian Huber wrote: Hello, even recent 32-bit architectures such as RISC-V do not support 64-bit atomic operations.  Using -fprofile-update=atomic for the 32-bit RISC-V RV32GC ISA yields: warning: target does not support atomic profile update, single mode is selecte

Re: -fprofile-update=atomic vs. 32-bit architectures

On 07.12.22 10:09, Richard Biener wrote: On Wed, Dec 7, 2022 at 9:51 AM Sebastian Huber wrote: On 06.12.22 17:08, Richard Biener wrote: Likely. I'd use the gimple_build () API from gimple-fold.h which builds the expression(s) to a gimple_seq creating necessary temporaries on-the-fly and t

Re: -fprofile-update=atomic vs. 32-bit architectures

On Wed, Dec 7, 2022 at 9:51 AM Sebastian Huber wrote: > > On 06.12.22 17:08, Richard Biener wrote: > > Likely. I'd use the gimple_build () API from gimple-fold.h which > > builds the expression(s) to a gimple_seq creating necessary temporaries > > on-the-fly and then insert that sequence on the e

Re: -fprofile-update=atomic vs. 32-bit architectures

On 06.12.22 17:08, Richard Biener wrote: Likely. I'd use the gimple_build () API from gimple-fold.h which builds the expression(s) to a gimple_seq creating necessary temporaries on-the-fly and then insert that sequence on the edge. Thanks, I will have a look at this. I am struggling to conver

Re: Spurious warning for zero-sized array parameters to a function

On Tue, Dec 6, 2022 at 5:22 PM Alejandro Colomar via Gcc wrote: > > Hi! > > In the following function, past_end is a pointer to one-past-the-end of the > array. Holding such a pointer is legal in C. I use it as a sentinel value > that > helps (1) avoid overrunning the buffer, and (2) detect tru